Device, Method, and Graphical User Interface for Synchronizing Two or More Displays

ABSTRACT

At a portable electronic device that includes a portable-device display and is in communication with a vehicle display, displaying a first user interface on the portable-device display. Sending, from the portable electronic device to the vehicle display, information for generating a second user interface, the second user interface including an affordance. While the second user interface is displayed on the vehicle display, detecting an input activating the affordance in the second user interface, and in response, causing the portable electronic device to invoke a digital assistant. In response to invoking the digital assistant, prompting a user for an audible request. In response to receiving the audible request, causing display, within the second user interface, of a digital assistant dialogue box; and subsequently causing display, within the second user interface, of a user interface object associated with a search result, and maintaining the first user interface on the portable-device display.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.15/971,458, filed May 4, 2018, which is a continuation of U.S.application Ser. No. 14/291,970, filed May 30, 2014, now U.S. Pat. No.9,965,035, which claims priority to U.S. Provisional Patent ApplicationNo. 61/832,842, filed Jun. 8, 2013, which applications are incorporatedherein by reference in their entirety.

This application is also related to the following applications: U.S.Provisional Application Ser. No. 61/793,924, filed Mar. 15, 2013,entitled “Voice and Touch User Interface;” U.S. application Ser. No.13/032,614, filed Feb. 22, 2011, now U.S. Pat. No. 8,970,647, entitled“Pushing a Graphical User Interface to a Remote Device with DisplayRules Provided by the Remote Device;” U.S. application Ser. No.12/683,218, filed Jan. 6, 2010, now abandoned, entitled “Pushing a UserInterface to a Remote Device;” U.S. application Ser. No. 12/119,960,filed May 13, 2008, now abandoned, entitled “Pushing a User Interface toa Remote Device;” U.S. application Ser. No. 13/175,581, filed Jul. 1,2011, now U.S. Pat. No. 9,870,130, entitled “Pushing a User Interface toa Remote Device;” U.S. application Ser. No. 13/161,339, filed Jun. 15,2011, now U.S. Pat. No. 9,311,115, entitled “Pushing a Graphical UserInterface to a Remote Device with Display Rules Provided by the RemoteDevice;” U.S. application Ser. No. 13/250,947, filed Sep. 30, 2011, nowU.S. Pat. No. 10,496,753, entitled “Automatically Adapting UserInterfaces for Hands-Free Interaction;” U.S. application Ser. No.12/987,982, filed Jan. 10, 2011, now U.S. Pat. No. 9,318,108, entitled“Intelligent Automated Assistant;” U.S. Provisional Application Ser. No.61/295,774, filed Jan. 18, 2010, entitled “Intelligent AutomatedAssistant;” U.S. Provisional Application Ser. No. 61/493,201, filed Jun.3, 2011, entitled “Generating and Processing Data Items that RepresentTasks to Perform;” U.S. Provisional Application Ser. No. 61/657,744,filed Jun. 9, 2012, entitled “Automatically Adapting User Interface forHands-Free Interaction;” U.S. application Ser. No. 12/207,316, filedSep. 9, 2008, now abandoned, entitled “Radio with Personal DJ;” U.S.Provisional Application Ser. No. 61/727,554, filed Nov. 16, 2012,entitled “System and Method for Negotiating Control of a Shared Audio orVisual Resource;” U.S. Application Ser. No. 61/832,818, filed Jun. 8,2013, entitled “Mapping Application with Several User Interfaces;” U.S.Provisional Application Ser. No. 61/832,841, filed Jun. 8, 2013,entitled “Device and Method for Generating User Interfaces from aTemplate;” and U.S. application Ser. No. 13/913,428, filed Jun. 8, 2013,now abandoned, entitled “Application Gateway for Providing DifferentUser Interfaces for Limited Distraction and Non-Limited DistractionContexts,” which applications are incorporated herein by reference intheir entirety.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that synchronize two or more displays.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touch pads and touchscreen displays. Such surfaces are widely used to manipulate userinterface objects on a first display associated with first electronicdevice.

Exemplary manipulations include adjusting the position and/or size ofone or more user interface objects or activating buttons or openingfiles/applications represented by user interface objects or otherwisemanipulating user interfaces. Exemplary user interface objects includedigital images, video, text, icons, control elements such as buttons andother graphics.

Sometimes users have access to multiple different displays that arecapable of displaying different content. For example, a passenger in acar or other vehicle may have access to a smart phone and its display,as well as access to a car information/entertainment system and itsdisplay(s). But when multiple different displays are available, methodsfor displaying content on these different displays are cumbersome andinefficient. For example, displaying the same information on thedifferent displays generally does not provide any useful additionalinformation to the user, while displaying unrelated information on thedifferent displays can be confusing and inefficient for the user andsometime causes the user to spend extra time keeping relevant contentdisplayed on both devices. In addition, these methods take longer thannecessary, thereby wasting energy. This latter consideration isparticularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with more efficientmethods and interfaces for synchronizing two or more displays. Suchmethods and interfaces optionally complement or replace conventionalmethods for displaying information on two or more displays. Such methodsand interfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated devices, suchmethods and interfaces conserve power and increase the time betweenbattery charges.

Additionally, in many situations controls for use in interacting withsuch user interfaces displayed on the displays are often rigidlyassociated with a single display. This limits the flexibility of thecontrols, which can result in an inefficient user interface.Accordingly, there is a need for a system that seamlessly maps controlsand other input sources to user interfaces displayed on differentdisplays in a flexible manner. However, when mapping different controlsto different displays, it would be easy to mistakenly associate acontrol with the wrong display. Moreover, taking a long time todetermine which display is associated with a particular control wouldintroduce a delay into the user's interactions with the user interfacethat would degrade the user experience. As such, there is a need for afast, accurate and efficient system and method for mapping controls andother input sources to different displays of the two or more displays.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, website creating, disk authoring, spreadsheet making, gameplaying, telephoning, video conferencing, e-mailing, instant messaging,workout support, digital photographing, digital videoing, web browsing,digital music playing, and/or digital video playing. Executableinstructions for performing these functions are, optionally, included ina non-transitory computer readable storage medium or other computerprogram product configured for execution by one or more processors.

In accordance with some embodiments, a method is performed at a firstelectronic device that includes a first display. The method includes:displaying a first user interface on the first display, where: the firstuser interface enables selection between a plurality of selectableobjects; the first user interface corresponds to a second user interfacedisplayed on a second display different from the first display; and afirst object from the plurality of selectable objects is displayed as aselected object in the second user interface. While the first object isdisplayed as the selected object in the second user interface, themethod includes: detecting a first input from a user that corresponds toa request to display information about a second object in the pluralityof selectable objects in the first user interface; in response todetecting the first input, updating the first user interface on thefirst display in accordance with the first input to display respectiveinformation about the second object while display of the first object asthe selected object in the second user interface is maintained; andafter updating the first user interface in accordance with the firstinput, detecting a second input from a user that corresponds to arequest to select the second object as the selected object. In responseto detecting the second input, the method further includes: updating thefirst user interface on the first display in accordance with the secondinput to display the second object as the selected object; andproviding, to the second display, information that enables the seconduser interface on the second display to be updated to display the secondobject as the selected object instead of the first object.

In accordance with some embodiments, a first electronic device includesa first display unit configured to display a first user interface on thefirst display unit, where: the first user interface enables selectionbetween a plurality of selectable objects; the first user interfacecorresponds to a second user interface displayed on a second displayunit different from the first display unit; and a first object from theplurality of selectable objects is displayed as a selected object in thesecond user interface. The first electronic device also includes aprocessing unit coupled to the first display unit. While the firstobject is displayed as the selected object in the second user interface,the processing unit is configured to: detect a first input from a userthat corresponds to a request to enable display of information about asecond object in the plurality of selectable objects in the first userinterface; in response to detecting the first input, update the firstuser interface on the first display unit in accordance with the firstinput to enable display of respective information about the secondobject while display of the first object as the selected object in thesecond user interface is maintained; and after updating the first userinterface in accordance with the first input, detect a second input froma user that corresponds to a request to select the second object as theselected object. In response to detecting the second input, theprocessing unit is further configured to: update the first userinterface on the first display unit in accordance with the second inputto enable display of the second object as the selected object; andprovide, to the second display unit, information that enables the seconduser interface on the second display unit to be updated to enabledisplay of the second object as the selected object instead of the firstobject.

In accordance with some embodiments, a method is performed at a portableelectronic device that includes a portable-device display and is incommunication with a vehicle display of a vehicle. The method includes:obtaining a set of map search results that includes a plurality ofcandidate destinations; displaying a portable-device navigationinterface on the portable-device display, where the portable-devicenavigation interface enables selection of a destination from theplurality of candidate destinations; and sending information to thevehicle display that enables the vehicle display to display a vehiclenavigation interface, where a first destination of the plurality ofcandidate destinations is a selected destination in the vehiclenavigation interface. While the first destination is the selecteddestination in the vehicle navigation interface, the method includes:detecting a first input from a user that corresponds to a request todisplay information about one or more candidate destinations in theplurality of candidate destinations other than the first destination; inresponse to detecting the first input, updating the portable-devicenavigation interface on the portable-device display in accordance withthe first input without the vehicle navigation interface on the vehicledisplay being updated; and after updating the portable-device navigationinterface in accordance with the first input, detecting a second inputfrom a user that corresponds to a request to select a second destinationin the plurality of candidate destinations as the selected destination.In response to detecting the second input, the method further includes:updating the portable-device navigation interface on the portable-devicedisplay in accordance with the second input to display the seconddestination as the selected destination; and sending information to thevehicle display that enables the vehicle display to update the vehiclenavigation interface in accordance with the second input to display thesecond destination as the selected destination.

In accordance with some embodiments, a portable electronic deviceincludes a portable-device display unit configured to display aportable-device navigation interface, a communications interface unitconfigured to communicate with a vehicle display unit of a vehicle, anda processing unit coupled to the portable-device display unit and thecommunications interface unit. The processing unit is configured to:obtain a set of map search results that includes a plurality ofcandidate destinations; enable display of the portable-device navigationinterface on the portable-device display unit, where the portable-devicenavigation interface enables selection of a destination from theplurality of candidate destinations; and send information to the vehicledisplay unit that enables the vehicle display unit to enable display ofthe vehicle navigation interface, where a first destination of theplurality of candidate destinations is a selected destination in thevehicle navigation interface. While the first destination is theselected destination in the vehicle navigation interface, the processingunit is also configured to: detect a first input from a user thatcorresponds to a request to enable display of information about one ormore candidate destinations in the plurality of candidate destinationsother than the first destination; in response to detecting the firstinput, update the portable-device navigation interface on theportable-device display unit in accordance with the first input withoutthe vehicle navigation interface on the vehicle display unit beingupdated; and after updating the portable-device navigation interface inaccordance with the first input, detect a second input from a user thatcorresponds to a request to select a second destination in the pluralityof candidate destinations as the selected destination. In response todetecting the second input, the processing unit is further configuredto: update the portable-device navigation interface on theportable-device display unit in accordance with the second input toenable display of the second destination as the selected destination;and send information to the vehicle display unit that enables thevehicle display unit to update the vehicle navigation interface inaccordance with the second input to enable display of the seconddestination as the selected destination.

In accordance with some embodiments, a method is performed at anelectronic device that is in communication with a plurality of displaysthat include a first display and a second display. The method includesreceiving first input information that is indicative of a first inputdetected by a first input source of a plurality of input sources, wherethe first input information includes: a first identifier for the firstinput source; and a first input description that describes the firstinput. The method also includes selecting a first affected display fromthe plurality of displays based on the first identifier and aninput-source mapping that maps input sources to corresponding displays.The method further includes sending, to the first affected display,update information that enables the first affected display to be updatedin accordance with the first input.

In accordance with some embodiments, an electronic device includes acommunications interface unit configured to communicate with a pluralityof display units that include a first display unit and a second displayunit, and a processing unit coupled to the communications interfaceunit. The processing unit is configured to receive a first inputinformation that is indicative of a first input detected by a firstinput source of a plurality of input sources, where the first inputinformation includes: a first identifier for the first input source; anda first input description that describes the first input. The processingunit is also configured to select a first affected display from theplurality of displays based on the first identifier and an input-sourcemapping that maps input sources to corresponding displays. Theprocessing unit is further configured to send, to the first affecteddisplay, update information that enables the first affected display tobe updated in accordance with the first input.

In accordance with some embodiments, an electronic device includes acommunications interface for communicating with one or more displays(e.g., a first display, a second display, a portable-device display,and/or a vehicle display), one or more processors, memory, and one ormore programs; the one or more programs are stored in the memory andconfigured to be executed by the one or more processors and the one ormore programs include instructions for performing the operations of anyof the methods described herein. In accordance with some embodiments, anon-transitory computer readable storage medium has stored thereininstructions which when executed by an electronic device that is incommunication with one or more displays, cause the device to perform theoperations of any of the methods referred described herein. Inaccordance with some embodiments, a graphical user interface on anelectronic device that is in communication with one or more displays, amemory, and one or more processors to execute one or more programsstored in the memory including one or more of the elements displayed inany of the methods described above, which are updated in response toinputs, as described in any of the methods described herein. Inaccordance with some embodiments, an electronic device that is incommunication with one or more displays includes means for performingthe operations of any of the methods described herein. In accordancewith some embodiments, an information processing apparatus, for use inan electronic device that is in communication with one or more displays,includes means for performing the operations of any of the methodsdescribed herein.

Thus, electronic devices with displays are provided with more efficientmethods and interfaces for synchronizing two or more displays, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceconventional methods for synchronizing two or more displays.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A is a block diagram illustrating an operating environment inwhich a portable multifunction device communicates with an externalpresentation system and/or server in accordance with some embodiments.

FIG. 5B is a flow diagram illustrating a method of sending updateinformation to an affected display in accordance with some embodiments.

FIGS. 6A-6V illustrate exemplary user interfaces for synchronizing twoor more displays in accordance with some embodiments.

FIGS. 6W-6FF illustrate exemplary user interfaces for sending updateinformation to an affected display in accordance with some embodiments.

FIGS. 7A-7D are flow diagrams illustrating a method of synchronizing twoor more displays in accordance with some embodiments.

FIGS. 8A-8B are flow diagrams illustrating a method of synchronizing twoor more displays in accordance with some embodiments.

FIGS. 9A-9C are flow diagrams illustrating a method of sending updateinformation to an affected display in accordance with some embodiments.

FIG. 10 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 11 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 12 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Many electronic devices update a graphical user interface on a displayassociated with the electronic device in response to the manipulation ofuser interface objects displayed on the display. The first electronicdevice described below improves on these methods by synchronizing (insome cases) a second graphical interface on a second display with afirst graphical user interface on a first display associated with thefirst electronic device. In some embodiments, the second display isassociated with a second electronic device different from the firstelectronic device. In some embodiments, the first electronic devicesynchronizes the first display and the second display in response tomanipulation of user interface objects on a first graphical userinterface (e.g., manipulated with a first touch-sensitive surface or afirst touch screen display associated with the first electronic device).In some other embodiments, the first electronic device synchronizes thefirst display and the second display in response to manipulation of userinterface objects on a second graphical user interface (e.g.,manipulated with a second touch-sensitive surface or a second touchscreen display associated with the second electronic device).

Below, FIGS. 1A-1B, 2, and 3 provide a description of exemplary devices.FIGS. 4A-4B and 6A-FF illustrate exemplary user interfaces. FIGS. 7A-7Dand 8A-8B are flow diagrams illustrating a method of synchronizing twoor more displays. FIGS. 9A-9C are flow diagrams illustrating a method ofsending update information to an affected display. The user interfacesin FIGS. 6A-6V are used to illustrate the processes in FIGS. 7A-7D and8A-8B. The user interfaces in FIGS. 6W-6FF are used to illustrate theprocesses in FIGS. 9A-9C.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or ‘upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touch pad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a touch-sensitive display system. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPU's) 120, peripherals interface 118, RF circuitry 108, audiocircuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem106, other input or control devices 116, and external port 124. Device100 optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on the touchsensitive surface, or to a substitute (proxy) for the force or pressureof a contact on the touch sensitive surface. The intensity of a contacthas a range of values that includes at least four distinct values andmore typically includes hundreds of distinct values (e.g., at least256). Intensity of a contact is, optionally, determined (or measured)using various approaches and various sensors or combinations of sensors.For example, one or more force sensors underneath or adjacent to thetouch-sensitive surface are, optionally, used to measure force atvarious points on the touch-sensitive surface. In some implementations,force measurements from multiple force sensors are combined (e.g., aweighted average) to determine an estimated force of a contact.Similarly, a pressure-sensitive tip of a stylus is, optionally, used todetermine a pressure of the stylus on the touch-sensitive surface.Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/or applicationspecific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU 120 and the peripherals interface118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over InternetProtocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet messageaccess protocol (IMAP) and/or post office protocol (POP)), instantmessaging (e.g., extensible messaging and presence protocol (XMPP),Session Initiation Protocol for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), Instant Messaging and Presence Service(IMPS)), and/or Short Message Service (SMS), or any other suitablecommunication protocol, including communication protocols not yetdeveloped as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161 and one or more input controllers 160 forother input or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, infrared port, USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 optionally capturesstill images or video. In some embodiments, an optical sensor is locatedon the back of device 100, opposite touch screen display 112 on thefront of the device, so that the touch screen display is enabled for useas a viewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained forvideoconferencing while the user views the other video conferenceparticipants on the touch screen display.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112 which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is coupled to input controller 160 inI/O subsystem 106. In some embodiments, the proximity sensor turns offand disables touch screen 112 when the multifunction device is placednear the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112 which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices116; and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices. In someembodiments, the external port is a multi-pin (e.g., 8-pin) connectorthat is the same as, or similar to and/or compatible with the 8-pinconnector (e.g., Lightning connector) used on iPhone and iPod (trademarkof Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and other touchsensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined thresholds values without changing thetrackpad or touch screen display hardware. Additionally, in someimplementations a user of the device is provided with software settingsfor adjusting one or more of the set of intensity thresholds (e.g., byadjusting individual intensity thresholds and/or by adjusting aplurality of intensity thresholds at once with a system-level click“intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   digital personal assistant module 150;    -   vehicle integration module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 are, optionally, used to manage an address book or contactlist (e.g., stored in application internal state 192 of contacts module137 in memory 102 or memory 370), including: adding name(s) to theaddress book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 are, optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in address book 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (e.g., using a Short Message Service (SMS) orMultimedia Message Service (MMS) protocol for telephony-based instantmessages or using XMPP, SIMPLE, or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo!© Widgets).

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, digital personalassistant module 150 records voice commands and sends informationrepresentative of the recorded voice commands to a server such as server510 in FIG. 5A for analysis, and responds to the voice commands based ona response from the server.

Vehicle integration module 151 includes executable instructions for oneor more intermediation processes that control a vehicle informationdisplay system in a vehicle (e.g., a car, a truck, a van, etc.) thatprovides a user interface on a respective display of the vehicleinformation display system (e.g., display 546 of external informationpresentation system 540 in FIG. 5A), such as for a mapping applicationor a music application. The vehicle integration application convertsinformation from third-party applications into content for display bythe vehicle integration application on the respective display of thevehicle information display system.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 are,optionally, used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-13, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysic allocation of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward)and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display (e.g., touch screendisplay 112). I/O interface 330 also optionally includes a keyboardand/or mouse (or other pointing device) 350 and touchpad 355, tactileoutput generator 357 for generating tactile outputs on device 300 (e.g.,similar to tactile output generator(s) 167 described above withreference to FIG. 1A), sensors 359 (e.g., optical, acceleration,proximity, touch-sensitive, and/or contact intensity sensors similar tocontact intensity sensor(s) 165 described above with reference to FIG.1A). Memory 370 includes high-speed random access memory, such as DRAM,SRAM, DDR RAM or other random access solid state memory devices; andoptionally includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 370optionally includes one or more storage devices remotely located fromCPU(s) 310. In some embodiments, memory 370 stores programs, modules,and data structures analogous to the programs, modules, and datastructures stored in memory 102 of portable multifunction device 100(FIG. 1A), or a subset thereof. Furthermore, memory 370 optionallystores additional programs, modules, and data structures not present inmemory 102 of portable multifunction device 100. For example, memory 370of device 300 optionally stores drawing module 380, presentation module382, word processing module 384, website creation module 386, diskauthoring module 388, and/or spreadsheet module 390, while memory 102 ofportable multifunction device 100 (FIG. 1A) optionally does not storethese modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that is, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof: Signal strengthindicator(s) 402 for wireless communication(s), such as cellular andWiFi signals;

-   -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser”; and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod.”    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Text”;        -   Icon 426 for calendar module 148, labeled “Calendar”;        -   Icon 428 for image management module 144, labeled “Photos”;        -   Icon 430 for camera module 143, labeled “Camera”;        -   Icon 432 for online video module 155, labeled “Online            Video”;        -   Icon 434 for stocks widget 149-2, labeled “Stocks”;        -   Icon 436 for map module 154, labeled “Map”;        -   Icon 438 for weather widget 149-1, labeled “Weather”;        -   Icon 440 for alarm clock widget 149-4, labeled “Clock”;        -   Icon 442 for workout support module 142, labeled “Workout            Support”;        -   Icon 444 for notes module 153, labeled “Notes”; and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 are labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments the touch sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementationsfocus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

FIG. 5A illustrates a block diagram of an operating environment 500 inaccordance with some embodiments. Operating environment 500 includes aserver 510, one or more communications networks 505, portablemultifunction device 100, and external information presentation system540. In some embodiments, external information presentation system 540is an entertainment and/or navigation system that is implemented in avehicle. In some embodiments, external information presentation system540 includes one or more displays. In some embodiments, a vehicleincludes a plurality of external information presentation system 540communicatively coupled to device 100 in operating environment 500 eachwith a respective display.

Server 510 typically includes one or more processing units (CPUs) 512for executing modules, programs and/or instructions stored in memory 524and thereby performing processing operations, one or more network orother communications interfaces 520, memory 524, and one or morecommunication buses 522 for interconnecting these components.Communication buses 522 optionally include circuitry (sometimes called achipset) that interconnects and controls communications between systemcomponents. Memory 524 includes high-speed random access memory, such asDRAM, SRAM, DDR RAM or other random access solid state memory devices,and may include non-volatile memory, such as one or more magnetic diskstorage devices, optical disk storage devices, flash memory devices, orother non-volatile solid state storage devices. Memory 524 optionallyincludes one or more storage devices remotely located from the CPU(s)512. Memory 524, or alternately the non-volatile memory device(s) withinmemory 524, comprises a non-transitory computer readable storage medium.In some embodiments, memory 524, or the computer readable storage mediumof memory 524 stores the following programs, modules, and datastructures, or a subset thereof:

-   -   an operating system 526 that includes procedures for handling        various basic system services and for performing hardware        dependent tasks; and    -   a network communication module 528 that is used for connecting        (wired or wireless) server 510 to other computing devices via        the one or more communication network interfaces 520 and one or        more communication networks 505, such as the Internet, other        wide area networks, local area networks, metropolitan area        networks, and so on.

Portable multifunction device 100 (sometimes herein also called “device100”) typically includes the components described with reference toFIGS. 1A-1B and/or 3.

External information presentation system 540 (sometimes herein alsocalled “system 540”) typically includes one or more processing units(CPUs) 542 for executing modules, programs and/or instructions stored inmemory 554 and thereby performing processing operations, one or morenetwork or other communications interfaces 550, memory 554, and one ormore communication buses 552 for interconnecting these components.External information presentation system 540, optionally, includes auser interface 544 comprising one or more display devices 546 and aplurality of controls 548 (e.g., jog dials, knobs, buttons, switches, atouch-sensitive surface such as a touch screen display, or other inputsources). In some embodiments, the one or more displays 546 include aprimary display 546-1 (e.g., a dashboard or vehicle navigation display)and an auxiliary display 546-2 (e.g., a rear-seat or entertainmentdisplay). In some embodiments, a respective display of the one or moredisplays 546 is a touch screen display that is capable of receiving usertouch inputs (e.g., detecting finger contacts and gestures thatcorrespond to the detection and movement of finger contacts). In someembodiments, a respective display of the one or more displays 546 isassociated with one or more controls of the plurality of controls 548(e.g., jog dials, knobs, buttons, switches, a touch-sensitive surfacesuch as a touch screen display, or other input sources). Communicationbuses 552 optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Memory 554 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM or other random access solid state memory devices, and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 554optionally includes one or more storage devices remotely located fromthe CPU(s) 542. Memory 552, or alternately the non-volatile memorydevice(s) within memory 552, comprises a non-transitory computerreadable storage medium. In some embodiments, memory 552, or thecomputer readable storage medium of memory 552 stores the followingprograms, modules, and data structures, or a subset thereof:

-   -   an operating system 556 that includes procedures for handling        various basic system services and for performing hardware        dependent tasks; and    -   a network communication module 558 that is used for connecting        (wired or wireless) server 540 to other computing devices via        the one or more communication network interfaces 550 and one or        more communication networks 505, such as the Internet, other        wide area networks, local area networks, metropolitan area        networks, and so on.

In some embodiments, device 100 drives the one or more displays 546 ofsystem 540. For example, device 100 sends a video signal to system 540,and CPU 542 of system 540 renders the video signal on the one or moredisplays 546. In some embodiments, device 100 sends a video signaldirectly to the one or more displays 546 and CPU 542 is not used torender the video signal (e.g., device 100 uses display 546 as anauxiliary display). In some embodiments, the user interface displayed ontouch screen 112 of device 100 is synchronized with the user interfacedisplayed on the one or more displays 546 of system 540, and, in someother embodiments, the user interface displayed on touch screen 112 ofdevice 100 is not continuously synchronized with the user interfacedisplayed on the one or more displays 546 of system 540 and at times(e.g., while a user of device 100 is viewing information about possibledriving destinations but has not yet selected a driving destination)touchscreen 112 of device 100 displays different information from thatdisplayed on display 546 of system 540 (e.g., touch screen 112 anddisplay 546 are intermittently synchronized with periods in between theintermittent synchronization events where they are not synchronized).

In some embodiments, in response to detecting a user input (e.g., a usertouch input associated with a respective display of the one or moredisplays 546 or a user input associated with a respective control of theplurality of controls 548), system 540 (or the respective display of theone or more displays 546, or the respective control of the plurality ofcontrols 548) sends input information (e.g., an identifier for the inputsource and an input description describing the user input) correspondingto the user input to device 100. In turn, device 100 updates the userinterface displayed on the respective display of the one or moredisplays 546 and/or touch screen 112 of device 100 in accordance withthe received input information and/or the display state of the userinterface displayed on the respective display of the one or moredisplays 546 at or before the user input.

FIG. 5B is a flow diagram illustrating a process of selecting anaffected display and sending update information to the affected display.The affected display (e.g., primary display 546-1) displays (560) a userinterface. A respective input source (e.g., jog dial 675 shown in FIGS.6W-6FF) that is a control of system 540 detects (561) a user input(e.g., rotation of jog dial 675). In some embodiments, the respectiveinput source is one of controls 548 and the user input is an interactionwith one of controls 548. For example, controls 548 include buttons,switches, dials, knobs, other mechanical affordances, touch-sensitivesurfaces, or other input sources. For example, the user input isrotation of a knob or dial, depression of an affordance or knob, a touchinput detected on a touch-sensitive surface or touch screen, or otheruser interaction with controls 548.

In response to detecting the user input, the respective input sourcesends (562) input information (e.g., {Source ID; Input Description}) todevice 100. In some embodiments, the input information includes a uniqueidentifier for the input source and input description information thatdescribes the user input. For example, the input description informationis raw input data such as the magnitude and direction of rotation of ajog dial, contact locations and movement amounts/directions detected ona touch-sensitive surface and/or gesture data describing a type ofgesture that was performed on the touch-sensitive surface.

Device 100 receives (564) the input information from the respectiveinput source. Device 100 selects an affected display by correlating theunique identifier (e.g., source ID) included in the input informationwith a display identifier tag (e.g., a display ID) based at least inpart on input-source mapping 566. In some embodiments, the input-sourcemapping 566 is stored in memory of device 100. For example, device 100associates rotation of jog dial 675 with a first display (e.g., display546-1 in FIGS. 6W-6CC) based on input-source mapping 566 when jog dial675 is associated with the first display. Alternatively, when jog dial675 is associated with a second display (e.g., display 546-2 in FIGS.6DD-6FF), device 100 associates rotation of jog dial 675 with the seconddisplay. In some embodiments, multiple inputs sources are mapped to asame display. However, in some embodiments, each input source is mappedno more than a single display. In some embodiments, input-source mapping566 is updated by device 100 in response to detectinginput-source-mapping update events (e.g., a vehicle associated with thefirst display starting to back up and taking control of the firstdisplay, or an input associating a jog dial with the second displayinstead of the first display) and/or in accordance with a predeterminedschedule.

After selecting the affected display, device 100 determines a respectivestate of the user interface displayed on the affected display bycorrelating the display ID (determined based on input-source mapping566) for the affected display with display state information (e.g., whatkind of user interface is displayed in the display, what user interfaceelements are displayed, and/or which controls are associated with whichfunctions such as volume control or scrolling) based at least in part onuser interface state table 568. In some embodiments, the user interfacestate table 568 is stored in memory of device 100. After determining therespective state of the user interface displayed on the affecteddisplay, device 100 generates (570) an updated user interface for theaffected display in accordance with the respective state of the userinterface displayed on the affected display and the input descriptioninformation, and device 100 sends the updated user interface (orinformation for generating an updated user interface) to the affecteddisplay. In some embodiments, device 100 also updates user interfacestate table 568 so that the state information associated with thedisplay ID corresponding to the affected display reflects the updateduser interface (e.g., for use in responding to subsequent inputinformation received from the input source).

In response to receiving the updated user interface (e.g., updateinformation) from device 100, the affected display updates (574), theuser interface displayed on the affected displayed so as to display theupdated user interface (e.g., by replacing an image of a user interfacepreviously provided by device 100 with an updated image of the userinterface provided by device 100 in the update information).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronic devicewith a display and a touch-sensitive surface, such as device 300 orportable multifunction device 100.

FIGS. 6A-6V illustrate exemplary user interfaces for synchronizing twoor more displays in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 7A-7D and 8A-8B.

FIG. 6A illustrates user interface 602 displayed on touch screen 112 ofportable multifunction device 100 (sometimes herein also called “device100”). User interface 602 includes a plurality of user interface objects(e.g., application icons 424, 426, 428, 430, 434, 436, 438, 446, 416,418, 420, and 422). FIG. 6A also illustrates detecting user touch input606 over the maps application icon 436 on touch screen 112.

FIG. 6A further illustrates user interface 604 displayed on display546-1 of external information presentation system 540 (sometimes hereinalso called “system 540”). In some embodiments, system 540 is includedin a vehicle (e.g., in the dashboard or steering wheel of the vehicle).In some embodiments, display 546-1 is a primary display of a pluralityof displays associated with system 540. In some embodiments, display546-1 is implemented in the dashboard of the vehicle and is visuallyaccessible to the driver and/or passenger of the vehicle. In someembodiments, display 546-1 is a touch screen display configured todetect one or more user touch inputs. FIG. 6A illustrates display 546-1displaying a plurality of climate controls in user interface 604including the outside temperature (e.g., 82°), the temperature in thedriver's zone of the vehicle (e.g., 70°), the temperature in thepassenger's zone of the vehicle (e.g., 75°), the fan intensity in thedriver's zone of the vehicle (e.g., 2 on a 0-10 scale), and the fanintensity in the passenger's zone of the vehicle (e.g., 5 on a 0-10scale). FIG. 6A also illustrates display 546-1 displaying a plurality ofuser interface objects (sometimes herein called “affordances” or“selectable user interface objects”) enabled to adjust the temperaturein a respective zone of the vehicle (e.g., affordances 603 a, 603 b, 603c, and 603 d), a plurality of user interface objects enabled to adjustthe fan intensity in a respective zone of the vehicle (e.g., affordances603 e, 603 f, 603 g, and 603 h), and a plurality of user interfaceobjects enabled to adjust other vehicle climate control settings (e.g.,affordances 605 a related to air conditioning, 605 b related towindshield defrost, 605 c related to rear window defrost, and 605 drelated to automatic climate control). FIG. 6A further illustrates aplurality of mechanical affordances configured to control the volume ofthe sound system of the vehicle or to scroll one or more user interfaceobjects on display 546-1 (e.g., knob or jog dial 607 c), and the radiotuner of the vehicle (e.g., affordances 607 a, 607 b, 607 d, and 607 e).

FIG. 6B illustrates touch screen 112 displaying current location 608 ofdevice 100 in a map application in user interface 602 of touch screen112 in response to detecting user touch input 606 over the mapsapplication icon 436 in FIG. 6A. In some embodiments detecting a usertouch input over a respective affordance corresponds to detecting a tapgesture on the respective affordance, where the tap gesture includesdetecting a contact at a location that corresponds to the respectiveaffordance and detecting liftoff of the contact within a predeterminedtime period (e.g., 0.05, 0.1, 0.2, 03, 0.4 or 0.5 seconds). In someembodiments, the map displayed in user interface 602 is not to scale.FIG. 6B also illustrates detecting user touch input 610 over search box609 on touch screen 112.

FIG. 6B further illustrates displaying, on display 546-1, a currentlocation 608 of device 100 in a map displayed in user interface 604 inresponse to detecting user touch input 606 over the maps applicationicon 436 in FIG. 6A. In some embodiments, the map displayed in userinterface 604 is not to scale. Affordance 612, also displayed in userinterface 604, when activated, causes the device to invoke a digitalassistant (e.g., Siri from Apple Inc. of Cupertino, Calif.). FIG. 6Balso illustrates compass 611 indicating the orientation of the mapdisplayed in user interface 604 (e.g., the map is oriented with the topof display 546-1 being north). In some implementations, the font size ofinformation displayed in user interface 604 of display 546-1 is largerthan the font size of information displayed in user interface 602 oftouch screen 112. For example, when system 540 is located in a vehicle,the text on display 546-1 is generated so as to be larger than on touchscreen 112 of device 100 to enable greater readability while the driverand passenger(s) of the vehicle are at arm's length of display 546-1.

FIG. 6C illustrates displaying a user search query (e.g., dry cleaning)input in search box 609 of user interface 602. In one example, the usermanually inputs the search query with a virtual keyboard in userinterface 602 of device 100. In another example, the search query is aspeech input received from the user of device 100. FIG. 6C furtherillustrates maintaining display of user interface 604 from FIG. 6B ondisplay 546-1.

FIG. 6D illustrates displaying user interface objects (e.g., pins)associated with the dry cleaners represented by pins 614 a and 614 bnearby current location 608 of device 100 in user interface 602 inresponse to input of the search query in FIG. 6C. In some embodiments, asearch result (or establishment) matching the user's search query isautomatically selected (e.g., ABC Cleaners) based on proximity, theestablishment's ratings, the amount of reviews, the amount of times theuser has frequented the establishment, and/or other factors. In FIG. 6D,information box 613 corresponding to automatically selected dry cleanerrepresented by pin 614 a is also displayed in user interface 602.Information box 613 includes the dry cleaning establishment's name(e.g., ABC Cleaners), the rating of the establishment (e.g., 3 out of 5stars), the amount of user reviews for the establishment (e.g., 100reviews), and affordance 613 a configured to display additionalinformation corresponding to the establishment. In some embodiments,information box 613, when activated, causes the device to displayadditional information corresponding to the establishment in response toa user touch input anywhere in information box 613. In some otherembodiments, information box 613, when activated, causes the device todisplay additional information corresponding to the establishment inresponse to a user touch input over affordance 613 a. FIG. 6D alsoillustrates detecting user touch input 615 over affordance 613 a ontouch screen 112.

FIG. 6D further illustrates displaying suggested route 616 from currentlocation 608 of device 100 to the automatically selected search result(e.g., dry cleaner represented by pin 614 a corresponding to ABCcleaners) in user interface 604 in response to input of the search queryin FIG. 6C. In FIG. 6D, user interface 604 includes route 616,turn-by-turn directions box 617 indicating the user's first direction(or turn) on route 616 and the name of the destination (e.g., ABCCleaners), and “start directions” affordance 618 configured to initiatea turn-by-turn direction mode in which the device would provideturn-by-turn directions to ABC Cleaners using visual and/or spokenprompts. FIG. 6D also illustrates compass 611 indicating the orientationof the map displayed in user interface 604 (e.g., the map is orientedwith the top of display 546-1 being south, so that the direction thatthe vehicle is instructed to drive in the turn-by-turn directions isoriented toward a top of display 546-1).

FIG. 6E illustrates displaying additional information corresponding toABC Cleaners in user interface 602 in response to detecting user touchinput 615 over affordance 613 a in FIG. 6D. In FIG. 6E, user interface602 includes information identifying the hours of operation of ABCCleaners, the home page (or website) for ABC Cleaners, the phone numberfor ABC Cleaners, and the address for ABC Cleaners. In FIG. 6E, userinterface 602 also includes affordance 619 configured to displaydirections from the device's current location to ABC Cleaners andaffordance 620 configured to display directions from ABC Cleaners to thedevice's current location. FIG. 6E also illustrates detecting user touchinput 621 over affordance 619 on touch screen 112. FIG. 6E furtherillustrates maintaining display of user interface 604 from FIG. 6D ondisplay 546-1.

FIG. 6F illustrates displaying an interface in user interface 602 forinputting a start point and an end point for a route in response todetecting user touch input 621 over affordance 619 on touch screen 112in FIG. 6E. In FIG. 6F, user interface 602 includes the address of thestart point of the route in box 622 a (e.g., the current location ofdevice 100) and the address of the end point of the route in box 622 b(e.g., ABC Cleaners, 1660 40th Avenue, San Francisco, Calif.). In FIG.6F, box 622 a and/or box 622 b are enabled to be edited with virtualkeyboard 624 displayed in user interface 602 or, alternatively, with aspeech input. Affordance 622 c, when activated, causes the device toreplace the location entered in box 622 a with the location in box 622 band to replace the location entered in box 622 b with the location inbox 622 a. In FIG. 6F, user interface 602 includes selectable routes 623from device 100's current location to previously entered destinations.In FIG. 6F, user interface 602 further includes affordances 627 a, 627b, and 627 c configured to select different modes of transportation forroute calculation. For example, in FIG. 6F, the “walk” mode oftransportation is currently selected as shown by the highlighted framearound affordance 627 b. FIG. 6F also illustrates displaying a “route”affordance 626 a configured to calculate one or more routes from thestart point in box 622 a to the end point in box 622 b and a “cancel”affordance 626 b configured to clear the locations entered in boxes 622a and 622 b or to redisplay user interface 602 displayed in FIG. 6D.FIG. 6F further illustrates detecting user touch input 628 over “route”affordance 626 a on touch screen 112. FIG. 6F further illustratesmaintaining display of user interface 604 from FIG. 6D on display 546-1.

FIG. 6G illustrates displaying two suggested routes from currentlocation 608 of device 100 to the dry cleaner represented by pin 614 ain user interface 602 in response to detecting user touch input 628 over“route” affordance 626 a on touch screen 112 in FIG. 6F. In FIG. 6G,dialogue box 629 indicates that the currently selected, first of twosuggested routes will take 10 minutes and 0.2 miles for the user to walkfrom the current location 608 of device 100 to the dry cleanerrepresented by pin 614 a. In FIG. 6G, the first route 631 a ishighlighted in user interface 602, and “route 1” affordance 631 b, whenactivated, causes the device to select (and highlight) route 631 a. InFIG. 6G, route 631 a displayed in user interface 602 is the same asroute 616 displayed in user interface 604 but in a differentorientation. FIG. 6G also illustrates displaying route 632 a in userinterface 602 and “route 2” affordance 632 b configured to select (andhighlight) route 632 a. In FIG. 6G, “start” affordance 630 a, whenactivated, causes the device to start turn-by-turn directions to thecurrently selected (or highlighted) route (e.g., route 631 a), and“clear” affordance 630 b, when activated, causes the device to clear thedisplayed routes (e.g., routes 631 a and 632 a) from user interface 602and to display search box 609 in user interface 602. FIG. 6G furtherillustrates detecting user touch input 633 over “start” affordance 630 aon touch screen 112. FIG. 6G further illustrates maintaining display ofuser interface 604 from FIG. 6D on display 546-1. In some embodiments,when device 100 is connected to display 546-1 and display 546-1 is avehicle display, device 100 displays driving directions rather thanwalking directions on both touch screen 112 and on display 546-1.

FIG. 6H illustrates displaying turn-by-turn directions box 634indicating the user's first direction (or turn) on route 631 a and thename of the destination (e.g., ABC Cleaners) in user interface 602 inresponse to detecting user touch input 633 over “start” affordance 630 ain FIG. 6G. In some embodiments, turn-by-turn directions box 634occupies the entirety of touch screen 112. FIG. 6H also illustratesdetecting user touch input 635 on touch screen 112.

FIG. 6H further illustrates displaying a turn-by-turn direction mode inuser interface 604 in response to device 100 detecting user touch input633 over start affordance 630 a in FIG. 6G. In FIG. 6H, while in theturn-by-turn mode, the current location of device 100 is displayed asmarker 636 in user interface 604. In some embodiments, the turn-by-turndirection mode displayed in FIG. 6H is further zoomed into the mapdisplayed in user interface 604 in comparison to the map displayed inFIGS. 6D-6G (e.g., the map displayed on touch screen 112 is at a lowermagnification level than the map displayed on display 546-1).

FIG. 61 illustrates displaying dialogue box 637 in user interface 602 inresponse to detecting user touch input 635 on touch screen 112 in FIG.6H. In FIG. 61, dialogue box 637 includes “pause” affordance 638 aconfigured to pause turn-by-turn directions and “back” affordance 638 bconfigured to display the results from the most recent search query(e.g., dry cleaners nearby device 100's current location) within mapsapplication 436. FIG. 61 also illustrates detecting user touch input 639over “back” affordance 638 b. FIG. 61 further illustrates maintainingdisplay of user interface 604 from FIG. 6H on display 546-1.

FIG. 6J illustrates displaying user interface objects (e.g., pins)associated with the dry cleaners represented by pins 614 a and 614 bnearby current location 608 of device 100 in user interface 602 (e.g.,corresponding to the most recent search query in maps application 436from FIG. 6C) in response to user touch input 639 (e.g., a tap input)over “back” affordance 638 b in FIG. 61. FIG. 6J also illustratesdetecting a pinch gesture that includes movement of contacts 640 and 641on touch screen 112. FIG. 6J further illustrates maintaining display ofuser interface 604 from FIG. 6H on display 546-1.

FIG. 6K illustrates displaying user interface objects (e.g., pins)associated with the dry cleaners represented by pins 614 a, 614 b, 614c, and 614 d nearby current location 608 of device 100 in user interface602 in response to detecting the pinch gesture in FIG. 6J. For example,in FIG. 6K, the map is zoomed out (e.g., displayed at a lowermagnification level) in response to the pinch gesture, and a larger areaof the map is displayed in user interface 602. FIG. 6K also illustratesdetecting a swipe gesture (sometimes herein also called a “draggesture”) with user touch input 642 moving from position 642 a toposition 642 b on touch screen 112. FIG. 6K further illustratesmaintaining display of user interface 604 from FIG. 6H on display 546-1(e.g., user interface 604 is not zoomed out in response to detecting thepinch gesture on touch screen display 112).

FIG. 6L illustrates displaying user interface objects (e.g., pins)associated with the dry cleaners represented by pins 614 a, 614 b, 614c, 614 e and 614 f nearby current location 608 of device 100 in userinterface 602 in response to detecting the swipe gesture in FIG. 6K. Forexample, the map is translated in a north-eastward direction in responseto the swipe gesture in FIG. 6K. FIG. 6L also illustrates detecting usertouch input 643 over the user interface object (e.g., the pin)associated with the dry cleaners represented by pins 614 b on touchscreen 112. FIG. 6L further illustrates maintaining display of userinterface 604 from FIG. 6H on display 546-1 (e.g., user interface 604 isnot scrolled in response to detecting the swipe gesture on touch screendisplay 112).

FIG. 6M illustrates displaying information box 644 corresponding to thedry cleaner represented by pin 614 b in user interface 602 in responseto detecting user touch input 643 over the user interface object (e.g.,the pin) associated with the dry cleaners represented by pins 614 b inFIG. 6L. In FIG. 6M, information box 644 includes the dry cleaningestablishment's name (e.g., Mary Ann's Cleaners), the rating of theestablishment (e.g., 5 out of 5 stars), the amount of user reviews forthe establishment (e.g., 927 reviews), and affordance 644 a optionallyincludes additional information corresponding to the establishment. FIG.6M also illustrates detecting user touch input 645 over affordance 644 aon touch screen 112. FIG. 6M further illustrates maintaining display ofuser interface 604 from FIG. 6H on display 546-1.

FIG. 6N illustrates displaying additional information corresponding toMary Ann's Cleaners in user interface 602 in response to detecting usertouch input 645 over affordance 644 a in FIG. 6M. In FIG. 6N, userinterface 602 includes information identifying the hours of operation ofMary Ann's Cleaners, the home page (or website) for Mary Ann's Cleaners,the phone number for Mary Ann's Cleaners, and the address for Mary Ann'sCleaners. In FIG. 6N, user interface 602 also includes affordance 646configured to display directions from the device's current location toMary Ann's Cleaners and affordance 647 configured to display directionsfrom Mary Ann's Cleaners to the device's current location. FIG. 6N alsoillustrates detecting user touch input 648 over affordance 646 on touchscreen 112. FIG. 6N further illustrates maintaining display of userinterface 604 from FIG. 6H on display 546-1.

FIG. 60 illustrates displaying an interface in user interface 602 forinputting a start point and an end point for a route in response todetecting user touch input 648 over affordance 646 on touch screen 112in FIG. 6N. In FIG. 60, user interface 602 includes the address of thestart point of the route in box 649 a (e.g., the current location ofdevice 100) and the address of the end point of the route in box 649 b(e.g., Mary Ann's Cleaners, 1291 Judah Street, San Francisco, Calif.).In FIG. 60, box 649 a and/or box 649 b are enabled to be edited withvirtual keyboard 651 displayed in user interface 602 or, alternatively,with a speech input. Affordance 649 c, when activated, causes the deviceto replace the location entered in box 649 a with the location in box649 b and to replace the location entered in box 649 b with the locationin box 649 a. In FIG. 60, user interface 602 includes selectable routes650 from the device's current location to previously entereddestinations. In FIG. 60, user interface 602 further includesaffordances 653 a, 653 b, and 653 c configured to select different modesof transportation for route calculation. For example, in FIG. 60, the“walk” mode of transportation is currently selected as shown by thehighlighted frame around affordance 653 b. FIG. 60 also illustratesdisplaying a “route” affordance 652 a configured to calculate one ormore routes from the start point in box 649 a to the end point in box649 b and a ‘cancel” affordance 652 b configured to clear the locationsentered in boxes 649 a and 649 b or to redisplay user interface 602displayed in FIG. 6M. FIG. 60 further illustrates detecting user touchinput 655 over “route” affordance 654 (e.g., an affordance included invirtual keyboard 651) on touch screen 112. In some embodiments, “route”affordance 654, when activated, causes the device to calculate and/ordisplay one or more routes from the start point in box 649 a to the endpoint in box 649 b (e.g., “route” affordance 654 functions similarly to“route” affordance 652 a). FIG. 60 further illustrates maintainingdisplay of user interface 604 from FIG. 6H on display 546-1.

FIG. 6P illustrates displaying two suggested routes from currentlocation 608 of device 100 to the dry cleaner represented by pin 614 bin user interface 602 in response to detecting user touch input 655 over“route” affordance 654 on touch screen 112 in FIG. 60. In FIG. 6P, userinterface 602 dialogue box 656 indicating that the automaticallyselected, first of two suggested routes will take 5 minutes and 0.4miles for the user to walk from current location 608 of device 100 tothe dry cleaner represented by pin 614 b. In FIG. 6P, the first route658 a is highlighted in user interface 602, and “route 1” affordance 658b, when activated, causes the device to select (and highlight) route 658b. In FIG. 6P, “start” affordance 657 a, when activated, causes thedevice to start turn-by-turn directions to the currently selected (orhighlighted) route (e.g., route 658 a), and “clear” affordance 657 b,when activated, causes the device to clear the displayed routes (e.g.,routes 658 a and 659 a) from user interface 602 and to display searchbox 609 in user interface 602. FIG. 6P further illustrates detectinguser touch input 660 over “route 2” affordance 659 b on touch screen112. FIG. 6P further illustrates maintaining display of user interface604 from FIG. 6H on display 546-1.

FIG. 6Q illustrates displaying route 659 a (route 2) as the selected (orhighlighted) route in response to detecting touch input 660 over “route2” affordance 659 b in FIG. 6P. In FIG. 6Q, user interface 602 includesdialogue box 656 indicating that the second of the two suggested routeswill take 6 minutes and 0.4 miles for the user to walk from currentlocation 608 of device 100 to the dry cleaner represented by pin 614 b.FIG. 6Q further illustrates detecting user touch input 661 over “start”affordance 657 a on touch screen 112. FIG. 6Q further illustratesmaintaining display of user interface 604 from FIG. 6H on display 546-1.

FIG. 6R illustrates displaying turn-by-turn directions box 662indicating the user's first direction (or turn) on route 659 a and thename of the destination (e.g., Mary Ann's Cleaners) in user interface602 in response to detecting user touch input 661 over “start”affordance 657 a in FIG. 6Q. In some embodiments, turn-by-turndirections box 662 occupies the entirety of touch screen 112.

FIG. 6R further illustrates displaying a turn-by-turn direction mode inuser interface 604 in response to detecting user touch input 661 over“start” affordance 657 a in FIG. 6Q (e.g., even though user interface604 was not previously synchronized with user interface 602 in responseto prior inputs, when a destination and route are selected andturn-by-turn directions commence, the device synchronizes user interface602 and user interface 604 so that both user interfaces show directionsto the same destination using the same route). In FIG. 6R, userinterface 604 includes route 659 a, turn-by-turn directions box 663indicating the user's first direction (or turn) on route 659 a and thename of the destination (e.g., Mary Ann's Cleaners), and marker 654indicating the current location of device 100. FIG. 6R also illustratescompass 611 indicating the orientation of the map displayed in userinterface 604 (e.g., the map is oriented with the top of display 546-1being east). FIG. 6R further illustrates detecting user touch input 665on display 546-1.

FIG. 6S illustrates displaying dialogue box 637 in user interface 602 inresponse to detecting user touch input 665 on display 546-1 in FIG. 6R.In FIG. 6S, dialogue box 637 includes “pause” affordance 638 aconfigured to pause turn-by-turn directions and “back” affordance 638 bconfigured to display the results from the most recent search query(e.g., dry cleaners nearby device 100's current location) within mapsapplication 436.

FIG. 6S further illustrates displaying affordance 612 in user interface604 in response to detecting user touch input 665 on display 546-1 inFIG. 6R. Affordance 612, when activated, causes the device to invoke adigital assistant (e.g., Siri from Apple Inc. of Cupertino, Calif.).FIG. 6S also illustrates detecting user touch input 666 over affordance612 on display 546-1. In response to detecting user touch input 666 overaffordance 612, a digital assistant is invoked, and the digitalassistant audibly prompts the user asking, “What may I help you with?”In response to the prompt, the user audibly, for example, asks thedigital assistant, “Show me nearby coffee houses.” Alternatively, insome embodiments, the digital assistant is invoked by a predeterminedaudible command (e.g., “Hey, Siri”).

FIG. 6T illustrates maintaining display of user interface 602 from FIG.6S on touch screen 112. FIG. 6T further illustrates displaying digitalassistant dialogue box 667 in user interface 604. digital assistantdialogue box 667 indicates that the digital assistant is searching forcoffee houses in response to the user's audible request (e.g., “Show menearby coffee houses.”).

FIG. 6U illustrates displaying user interface objects (e.g., pins)associated with coffee houses 668 a and 668 b nearby current location608 of device 100 in user interface 602 in response to the user'saudible request (e.g., “Show me nearby coffee houses.”). In someembodiments, a search result (or establishment) matching the audiblerequest is automatically selected (e.g., Java Haus) based on proximity,the establishment's ratings, the amount of reviews, the amount of timesthe user has frequented the establishment, and/or other factors. In FIG.6U, information box 669 corresponding to automatically selected coffeehouse 668 a is also displayed in user interface 602. Information box 669includes the coffee house's name (e.g., Java Haus), the rating of theestablishment (e.g., 4 out of 5 stars), the amount of user reviews forthe establishment (e.g., 320 reviews), and affordance 669 a configuredto display additional information corresponding to the establishment.Providing additional information in user interface 602 enables apassenger of a vehicle who is operating device 100 to provide additionalinformation to a driver of the vehicle and/or select a destination basedon the additional information provided in user interface 602.

FIG. 6U further illustrates displaying suggested route 671 from thecurrent location 608 of device 100 to coffee house 668 a (e.g., JavaHaus) in user interface 604 in response to the user's audible request(e.g., “Show me nearby coffee houses.”). In some embodiments, a routefor the automatically selected search result is displayed in userinterface 604. In FIG. 6U, user interface 604 includes route 671,turn-by-turn directions box 670 indicating the user's first direction(or turn) on route 671 and the name of the destination (e.g., JavaHaus), and “start directions” affordance 618 configured to initiate aturn-by-turn mode. FIG. 6U also illustrates compass 611 indicating theorientation of the map displayed in user interface 604 (e.g., the map isoriented with the top of display 546-1 being north). FIG. 6U furtherillustrates detecting user touch input 672 over “start directions”affordance 618 on display 546-1.

FIG. 6V illustrates displaying turn-by-turn directions box 673indicating the user's first direction (or turn) on route 671 and thename of the destination (e.g., Java Haus) in user interface 602 inresponse to detecting user touch input 672 over “start directions”affordance 662 on display 546-1 in FIG. 6U. In some embodiments,turn-by-turn directions box 673 occupies the entirety of touch screen112.

FIG. 6V further illustrates displaying a turn-by-turn direction mode inuser interface 604 in response detecting user touch input 672 over“start directions” affordance 662 on display 546-1 in FIG. 6U. In FIG.6V, while in the turn-by-turn mode, the current location of device 100is displayed as marker 674 in user interface 604. In some embodiments,the turn-by-turn direction mode displayed in FIG. 6V is further zoomedinto the map displayed in user interface 604 in comparison to the mapdisplayed in FIG. 6U.

FIGS. 6W-6FF illustrate exemplary user interfaces for sending updateinformation to an affected display in accordance with some embodiments.The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIGS. 9A-9C.

FIG. 6W illustrates two displays included in an external informationpresentation system 540 (sometimes herein also called “system 540”) thatis communicatively coupled to portable multifunction device 100(sometimes herein also called “device 100”) in accordance with someembodiments. In some embodiments, external information presentationsystem 540 is an entertainment and/or navigation system that isimplemented in a vehicle. In some embodiments, display 546-1 isassociated with a first external information presentation system 540-1,and display 546-2 is associated with a second external informationpresentation system 540-2. In some embodiments, display 546-1 is aprimary display (e.g., a dashboard or vehicle navigation display), anddisplay 546-2 is an auxiliary display (e.g., a rear-seat orentertainment display). In some embodiments, display 546-1 and display546-2 are touch-sensitive displays with touch-sensitive surfaces on thedisplays and are configured to receive one or more touch inputs. FIG. 6Walso illustrates jog dial 675 (e.g., a depressible and/or rotatablemechanical knob or dial) associated with system 540 configured tocontrol one or both of display 546-1 and display 546-2.

FIG. 6W illustrates displaying user interface objects (e.g., pins)associated with the dry cleaners represented by pins 614 a and 614 bnearby current location 608 of device 100 in a map/navigationapplication in user interface 604 of display 546-1. For example, thepins are displayed in user interface 604 in response a search query(e.g., “dry cleaning” input into search box 609 in user interface 602 ofdevice 100 in FIG. 6C). In some embodiments, a search result (orestablishment) matching the user's search query is automaticallyselected (e.g., ABC Cleaners) based on proximity, the establishment'sratings, the amount of reviews, the amount of times the user hasfrequented the establishment, and other factors. In FIG. 6W, destinationinformation 678 corresponding to automatically selected the dry cleanerrepresented by pin 614 a is also displayed in user interface 604.Destination information 678 includes the dry cleaning establishment'sname (e.g., ABC Cleaners), the rating of the establishment (e.g., 3 outof 5 stars), the amount of user reviews for the establishment (e.g., 100reviews), and the mileage from current location 608 of device 100 to theestablishment. In some embodiments, turn-by-turn directions to thecurrently selected search result (e.g., the dry cleaner represented bypin 614 a) are displayed in user interface 604 in response to a touchinput anywhere inside of the dialogue box associated with destinationinformation 678 corresponding to dry cleaner 514 a. In some otherembodiments, turn-by-turn directions to the currently selected searchresult (e.g., the dry cleaner represented by pin 614 a) are displayed inuser interface 604 in response to depression of jog dial 675. FIG. 6Walso illustrates compass 611 indicating the orientation of the mapdisplayed in user interface 604 (e.g., the map is oriented with the topof display 546-1 being north).

FIG. 6W illustrates detecting a pinch gesture with user touch inputs 679and 680 on display 546-1. In response to detecting user touch inputs 679and 680 (or the pinch gesture), display 546-1 (or system 540) sendsinput information indicative of user touch inputs 679 and 680 (or thepinch gesture) to device 100. The input information includes anidentifier associated with the touch-sensitive surface of display 546-1(e.g., a unique identifier associated with the touch-sensitive surfaceof display 546-1) and input description information describing usertouch inputs 679 and 680 (or the pinch gesture). In some embodiments,input description information includes raw data describing user touchinputs 679 and 680 such as the location of user touch inputs 679 and680, the magnitude of the movement of user touch inputs 679 and 680, thelength of time that user touch inputs 679 and 680 were detected, thesurface area of user touch inputs 679 and 680, and/or other informationdescribing user touch inputs 679 and 680. In some other embodiments,input description information includes data describing the pinch gesturesuch as the type of gesture performed, the location of the gesture, themagnitude of the movement of the gesture, and/or other informationdescribing the gesture.

In response to receiving the input information associated with usertouch inputs 679 and 680 (or the pinch gesture), device 100 determinesthat the identifier included in the input information is associated withdisplay 546-1 (e.g., associating the touch event (or the gesture) withthe touch-sensitive surface of display 546-1) based on an input-sourceto display mapping. After determining that the touch event detected inFIG. 6W is associated with display 546-1 (e.g., the affected display),device 100 also determines the display state of display 546-1 shown inFIG. 6W (e.g., user interface 604 is in a search results or destinationselection mode). In some embodiments, device 100 determines the displaystate of a display based on information included in the inputinformation. In some other embodiments, device 100 determines thedisplay state of a display by querying system 540 for such information.

FIG. 6W further illustrates displaying a list of songs 677 correspondingto an album in a media player application in user interface 676 ofdisplay 546-2.

FIG. 6X illustrates displaying user interface objects (e.g., pins)associated with the dry cleaners represented by pins 614 a, 614 b, 614c, and 614 d nearby current location 608 of device 100 in user interface604 of display 546-1. For example, the map displayed in user interface604 in FIG. 6X is a zoomed out version of the map displayed in userinterface 604 in FIG. 6W. Display 546-1 displays a zoomed out map inuser interface 604 in FIG. 6X in response to receiving updateinformation from device 100 including an updated user interfacecorresponding to the pinch gesture detected on display 546-1 in FIG. 6Wand the display state of user interface 604 in FIG. 6W (e.g., the searchresults or destination selection mode).

FIG. 6X also illustrates detecting turn 681 (e.g., an approximately 90degree clockwise turn) of jog dial 675. In response to detecting turn681, jog dial 675 (or system 540) sends input information indicative ofturn 681 to device 100. The input information includes an identifierassociated with jog dial 675 (e.g., a unique identifier associated withjog dial 675) and input description information describing turn 681. Forexample, the input description information includes raw data describingturn 681 such as the magnitude (90 degrees) and direction (clockwise) ofthe turn. In response to receiving the input information associated withturn 681, device 100 determines that the identifier included in theinput information is associated with display 546-1 (e.g., associatingthe turn event with jog dial 675 which is currently mapped to display546-1) based on the input-source to display mapping. After determiningthat the turn event detected in FIG. 6X is associated with display546-1, device 100 also determines the display state of display 546-1shown in FIG. 6X (e.g., user interface 604 is in a search results ordestination selection mode). FIG. 6X further illustrates maintainingdisplay of the list of songs 677 in user interface 676 from FIG. 6W ondisplay 546-2 (e.g., user interface 676 is not updated in response torotation of jog dial 675 when jog dial 675 is not associated with thedisplay on which user interface 676 is displayed).

FIG. 6Y illustrates displaying destination information 682 correspondingto selected the dry cleaner represented by pin 614 d in user interface604 of display 546-1. In FIG. 6Y, display 546-1 displays destinationinformation 682 corresponding to selected the dry cleaner represented bypin 614 d (e.g., Suzie's Cleaners) in response to receiving updateinformation from device 100 including an updated user interfacecorresponding to turn 681 detected by jog dial 675 in FIG. 6X and thedisplay state of user interface 604 in FIG. 6X (e.g., the search resultsor destination selection mode). In some embodiments, the destinationinformation (and hence the selected destination) is scrolled inaccordance with the direction and magnitude of the turn of jog dial 675.For example, when search results or a destination selection mode isdisplayed, a 90 degree turn of jog dial 675 selects a next searchresult, a clockwise turn scrolls the search results north-to-south, anda counter-clockwise turn scrolls the search results south-to-north. InFIG. 6Y, in response to detecting turn 681 (e.g., a 90 degree clockwiseturn) of jog dial 675 in FIG. 6X, the dry cleaner represented by pin 614d is selected (or scrolled to) and destination information 682corresponding to the dry cleaner represented by pin 614 d (e.g., thenext dry cleaner south of the dry cleaner represented by pin 614 adisplayed in FIG. 6X) is displayed in user interface 604.

FIG. 6Y also illustrates detecting turn 683 (e.g., an approximately 180degree counter-clockwise turn) of jog dial 675. In some embodiments, inresponse to detecting turn 683, jog dial 675 (or system 540) sends inputinformation indicative of turn 683 to device 100. The input informationincludes an identifier associated with jog dial 675 (e.g., a uniqueidentifier associated with jog dial 675) and input descriptioninformation describing turn 683. For example, the input descriptioninformation includes raw data describing turn 683 such as the magnitude(180 degrees) and direction (counter-clockwise) of the turn. In responseto receiving the input information associated with turn 683, device 100determines that the identifier included in the input information isassociated with display 546-1 (e.g., associating the turn event with jogdial 675 which is currently mapped to display 546-1) based on theinput-source to display mapping. After determining that the turn eventdetected in FIG. 6Y is associated with display 546-1, device 100 alsodetermines the display state of display 546-1 shown in FIG. 6Y (e.g.,user interface 604 is in a search results or destination selectionmode). FIG. 6Y further illustrates maintaining display of the list ofsongs 677 in user interface 676 from FIG. 6W on display 546-2.

FIG. 6Z illustrates displaying destination information 684 correspondingto selected the dry cleaner represented by pin 614 b (e.g., Mary Ann'sCleaners) in user interface 604 of display 546-1. In FIG. 6Z, display546-1 displays destination information 684 corresponding to selected thedry cleaner represented by pin 614 b in response to receiving updateinformation from device 100 including an updated user interfacecorresponding to turn 683 detected by jog dial 675 in FIG. 6Y and thedisplay state of user interface 604 in FIG. 6Y (e.g., the search resultsor destination selection mode). In FIG. 6Z, in response to detectingturn 683 (e.g., an 180 degree counter-clockwise turn) of jog dial 675 inFIG. 6Y, the dry cleaner represented by pin 614 b is selected (orscrolled to) and destination information 684 corresponding to the drycleaner represented by pin 614 b (e.g., two dry cleaners to the north ofthe dry cleaner represented by pin 614 d displayed in FIG. 6Y) isdisplayed in user interface 604.

FIG. 6Z also illustrates detecting a press on, or depression of, jogdial 675 with user touch input 685. In some embodiments, in response todetecting user touch input 685, jog dial 675 (or system 540) sends inputinformation indicative of user touch input 685 to device 100. The inputinformation includes an identifier associated with jog dial 675 (e.g., aunique identifier associated with jog dial 675) and input descriptioninformation describing user touch input 685. For example, the inputdescription information includes raw data describing user touch input685 such as the force of the input and the amount of depression of jogdial 675. In response to receiving the input information associated withuser touch input 685, device 100 determines that the identifier includedin the input information is associated with display 546-1 (e.g.,associating the press or depression event with jog dial 675 which iscurrently mapped to display 546-1) based on an input-source to displaymapping. After determining that the depression event detected in FIG. 6Zis associated with display 546-1, device 100 also determines the displaystate of display 546-1 shown in FIG. 6Z (e.g., user interface 604 is ina search results or destination selection mode). FIG. 6Z furtherillustrates maintaining display of the list of songs 677 in userinterface 676 from FIG. 6W on display 546-2.

FIG. 6AA illustrates displaying a turn-by-turn direction mode frommarker 664 indicating the current location of device 100 to the drycleaner represented by pin 614 b (e.g., Mary Ann's Cleaners) in userinterface 604 of display 546-1. In FIG. 6AA, display 546-1 displays theturn-by-turn direction mode in user interface 604 in response toreceiving update information from device 100 including an updated userinterface corresponding to user touch input 685 detected by jog dial 675in FIG. 6Z and the display state of user interface 604 in FIG. 6Z (e.g.,the search results or destination selection mode). In FIG. 6AA, inresponse to detecting user touch input 685 depressing jog dial 675 inFIG. 6Z, turn-by-turn directions from marker 664 indicating the currentlocation of device 100 to the dry cleaner represented by pin 614 b(e.g., selected with turn 683 of jog dial 675 in FIG. 6Y) on route 659 aare displayed in turn-by-turn directions box 663 in user interface 604.FIG. 6AA also illustrates compass 611 indicating the orientation of themap displayed in user interface 604 (e.g., the map is oriented with thetop of display 546-1 being east).

FIG. 6AA also illustrates detecting turn 686 (e.g., an approximately 90degree counter-clockwise turn) of jog dial 675. In response to detectingturn 686, jog dial 675 (or system 540) sends input informationindicative of turn 686 to device 100. The input information includes anidentifier associated with jog dial 675 (e.g., a unique identifierassociated with jog dial 675) and input description informationdescribing turn 686. For example, the input description informationincludes raw data describing turn 686 such as the magnitude (90 degrees)and direction (counter-clockwise) of the turn. In response to receivingthe input information associated with turn 681, device 100 determinesthat the identifier included in the input information is associated withdisplay 546-1 (e.g., associating the turn event with jog dial 675 whichis currently mapped to display 546-1) based on the input-source todisplay mapping. After determining that the turn event detected in FIG.6AA is associated with display 546-1, device 100 also determines thedisplay state of display 546-1 shown in FIG. 6AA (e.g., user interface604 is in a turn-by-turn directions mode). FIG. 6AA further illustratesmaintaining display of the list of songs 677 in user interface 676 fromFIG. 6W on display 546-2.

FIG. 6BB illustrates displaying a turn-by-turn direction mode in userinterface 604 of display 546-1. For example, the turn-by-turn directionmode displayed in user interface 604 in FIG. 6BB is a zoomed out versionof the turn-by-turn direction mode displayed in user interface 604 inFIG. 6AA. In FIG. 6BB, display 546-1 displays the zoomed outturn-by-turn direction mode in user interface 604 in FIG. 6BB inresponse to receiving update information from device 100 including anupdated user interface corresponding to turn 686 detected by jog dial675 in FIG. 6AA and the display state of user interface 604 in FIG. 6AA(e.g., the turn-by-turn directions mode). FIG. 6BB further illustratesmaintaining display of the list of songs 677 in user interface 676 fromFIG. 6W on display 546-2.

FIG. 6CC illustrates displaying a vehicle backup mode in user interface604 of display 546-1. For example, the vehicle backup mode displayed inuser interface 604 includes a video feed from a backup cameraimplemented in the vehicle. In some embodiments, the vehicle backup modeoccupies the entirety of display 546-1. When system 540 is implementedin a vehicle, display 646-1 displays a vehicle backup mode in userinterface 604 while the vehicle is in reverse. In some embodiments, thevehicle backup mode supersedes all update information received bydisplays 546-1 and 546-2 from device 100. In some embodiments, thevehicle backup mode is displayed on one of the displays (e.g., display546-1) but not on the other display (e.g., display 546-2).

Similarly, FIG. 6CC also illustrates displaying a vehicle backup mode inuser interface 676 of display 546-2. For example, the vehicle backupmode displayed in user interface 676 includes a video feed from thebackup camera implemented in the vehicle. In some embodiments, thevehicle backup mode occupies the entirety of display 546-2. When system540 is implemented in a vehicle, display 646-2 displays a vehicle backupmode in user interface 676 while the vehicle is in reverse. In someother embodiments, display 646-2 does not display the vehicle backupmode in user interface 676 and maintains display of interface 676 whilethe vehicle is in reverse.

FIG. 6DD illustrates displaying a turn-by-turn direction mode in userinterface 604 from 6BB on display 546-1 once the vehicle is no longer inreverse.

FIG. 6DD also illustrates detecting turn 688 (e.g., an approximately 90degree clockwise turn) of jog dial 675. In response to detecting turn688, jog dial 675 (or system 540) sends input information indicative ofturn 688 to device 100. The input information includes an identifierassociated with jog dial 675 (e.g., a unique identifier associated withjog dial 675) and input description information describing turn 688. Forexample, the input description information includes raw data describingturn 688 such as the magnitude (90 degrees) and direction (clockwise) ofthe turn.

Device 100 detects a change in the input-source to display mapping thatmaps jog dial 675 to display 546-2, instead of display 546-1. Forexample, device 100 changes the input-source to display mapping based oncommunications from external information presentation system 540 (e.g.,taking control of a display to show an output of a backup camera) orinput-source-mapping update request such as a user switching arespective control from a first display mode in which the respectivecontrol controls a user interface in the first display to asecond-display mode in which the respective control controls a userinterface in the second display. In response to receiving the inputinformation associated with turn 688, device 100 determines that theidentifier included in the input information is associated with display546-2 (e.g., associating the turn event with jog dial 675 which iscurrently mapped to display 546-2) based on the changed input-source todisplay mapping. After determining that the turn event detected in FIG.6DD is associated with display 546-2, device 100 also determines thedisplay state of display 546-2 shown in FIG. 6DD (e.g., user interface676 is in an album song list mode).

FIG. 6DD further illustrates returning to display the list of songs 677in user interface 676 from FIG. 6W on display 546-2 once the vehicle isno longer in reverse.

FIG. 6EE illustrates displaying the turn-by-turn direction mode in userinterface 604 from 6BB on display 546-1. FIG. 6EE also illustratesdisplaying a scrolled downward list of songs 677 in user interface 676of display 546-2. In FIG. 6EE, display 546-2 displays the scrolleddownward list of songs 677 in user interface 676 in response toreceiving update information from device 100 including an updated userinterface corresponding to turn 688 detected by jog dial 675 in FIG. 6DDand the display state of user interface 676 in FIG. 6DD (e.g., the albumsong list mode). In FIG. 6EE, in response to detecting turn 688 (e.g.,an approximately 90 degree clockwise turn) of jog dial 675 in FIG. 6DD,list of songs 677 is scrolled downward in user interface 604.

FIG. 6EE further illustrates detecting an upward swipe gesture(sometimes herein also called a “drag” gesture) with user touch input689 moving from position 689 a to position 689 b on display 546-2. Inresponse to detecting user touch input 689 (or the swipe gesture),display 546-2 (or system 540) sends input information indicative oftouch input 689 (or the swipe gesture) to device 100. The inputinformation includes an identifier associated with the touch-sensitivesurface of display 546-2 (e.g., a unique identifier associated with thetouch-sensitive surface of display 546-2) and input descriptioninformation describing touch input 689 (or the swipe gesture). Inresponse to receiving the input information associated with touch input689 (or the swipe gesture), device 100 determines that the identifierincluded in the input information is associated with display 546-2(e.g., associating the touch event (or the gesture) with thetouch-sensitive surface of display 546-2) based on the input-source todisplay mapping. After determining that the touch event detected in FIG.6EE is associated with display 546-2, device 100 also determines thedisplay state of display 546-2 shown in FIG. 6EE (e.g., user interface676 is in the album song list mode).

FIG. 6FF illustrates displaying the turn-by-turn direction mode in userinterface 604 from 6BB on display 546-1. FIG. 6FF also illustratesdisplaying a scrolled upward list of songs 677 in user interface 676 ofdisplay 546-2. In FIG. 6FF, display 546-2 displays the scrolled upwardlist of songs 677 in user interface 604 in response to receiving updateinformation from device 100 including an updated user interfacecorresponding to the swipe gesture detected on display 546-2 in FIG. 6EEand the display state of user interface 676 in FIG. 6EE (e.g., the albumsong list mode). In FIG. 6FF, in response to detecting the upward swipegesture in FIG. 6EE, list of songs 677 is scrolled upward in userinterface 604.

FIGS. 7A-7D are flow diagrams illustrating a method 700 of synchronizingtwo or more displays in accordance with some embodiments. Method 700 isperformed at a first electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a first display and atouch-sensitive surface. In some embodiments, the first display is atouch screen display (e.g., touch screen 112) and the touch-sensitivesurface is on the first display. In some embodiments, the first displayis separate from the touch-sensitive surface. Some operations in method700 are, optionally, combined and/or the order of some operations is,optionally, changed.

As described below, method 700 provides an intuitive way to synchronizetwo or more displays. The method reduces the cognitive burden on a userwhen displaying information on two or more displays, thereby creating amore efficient human-machine interface. For battery-operated electronicdevices, enabling a user to use information displayed on two or moredisplays faster and more efficiently conserves power and increases thetime between battery charges.

The first electronic device displays (702) a first user interface on thefirst display. In some embodiments, the first electronic device is aportable multifunction computing device such as a smart phone or tabletcomputer. FIGS. 6A-6V, for example, show portable multifunction device100 (sometimes herein called “device 100”) displaying user interface 602(e.g., the first user interface) on touch screen 112.

The first user interface enables (704) selection between a plurality ofselectable objects (e.g., search results that correspond to a previouslyperformed search operation). FIG. 6D, for example, shows user interfaceobjects (e.g., pins) corresponding to the dry cleaners represented bypins 614 a and 614 b displayed in user interface 602 of device 100. Thedry cleaners represented by pins 614 a and 614 b are displayed in userinterface 602 in FIG. 6D in response to a search query for “drycleaning” nearby the current location 608 of device 100 in FIG. 6C.

The first user interface corresponds to a second user interfacedisplayed on a second display different from the first display. In someembodiments, the first user interface and the second user interface areuser interfaces for a same respective application (e.g., an applicationrunning on the first electronic device). User interface 602 (e.g., thefirst user interface) displayed on touch screen 112 of device 100corresponds to user interface 604 (e.g., the second user interface)displayed on display 546-1 (e.g., a touch screen display) of externalinformation presentation system 540 (sometimes herein called “system540”). In some embodiments, display 546-1 is a primary display of aplurality of displays associated with system 540. In some embodiments,display 546-1 is implemented in the dashboard of the vehicle and isvisually accessible to the driver and/or passenger of the vehicle.

A first object from the plurality of selectable objects is displayed asa selected object in the second user interface (e.g., the first userobject is a currently selected object in the second user interface).FIG. 6D, for example, shows information box 613 corresponding to the drycleaner represented by pin 614 a displayed in user interface 602.Information box 613 is displayed in user interface 602 due to the factthat the dry cleaner represented by pin 614 a is automatically selectedbased on predetermined criteria. FIG. 6D, for example, further showsroute 616 from the current location 608 of device 100 to automaticallyselected the dry cleaner represented by pin 614 a displayed in userinterface 604 of display 546-1.

In some embodiments, the first object was automatically selected (706)as the selected object based on predefined object selection criteria(e.g., after initiating a search and receiving a set of one or moresearch results, a first object that corresponds to the most relevantsearch result was automatically, without user intervention, selected asthe selected object). In FIG. 6D, for example, the dry cleanerrepresented by pin 614 a is automatically selected based on proximity,the establishment's ratings, the amount of reviews, the amount of timesthe user has frequented the establishment, and/or other factors.

In some embodiments, the plurality of selectable objects correspond to(708) a plurality of search results produced in response to a searchquery (e.g., a typed or spoken search query), and the selected objectcorresponds to a currently selected search result. In FIG. 6D, forexample, user interface objects (e.g., pins) corresponding to the drycleaners represented by pins 614 a and 614 b are displayed in userinterface 602 of device 100 in response to the search query “drycleaning” input into search box 609 in FIG. 6C. In some embodiments, thesearch query is manually input into search box 609 by way of a virtualkeyboard displayed in user interface 602 of touch screen 112. In someother embodiments, the search query is audibly input into search querybox 609 by way of a speech input from the user of device 100. In FIG.6D, for example, the dry cleaner represented by pin 614 a isautomatically selected from the plurality of search results includingthe dry cleaners represented by pins 614 a and 614 b. Also, in FIG. 6D,user interface 604 of system 540 displays route 616 from currentlocation 608 of user device 100 to selected the dry cleaner representedby pin 614 a.

In some embodiments, the plurality of selectable objects correspond to(710) a plurality of map locations, and the selected object correspondsto a currently selected destination. In FIG. 6D, for example, userinterface objects (e.g., pins) corresponding to the dry cleanersrepresented by pins 614 a and 614 b are map locations relative tocurrent location 608 of device 100. Also, in FIG. 6D, user interface 604of system 540 displays route 616 from current location 608 of userdevice 100 to the map location for selected the dry cleaner representedby pin 614 a.

In some embodiments, the plurality of selectable objects correspond to(712) a plurality of navigation routes, and the selected objectcorresponds to a currently selected navigation route. FIG. 6G, forexample, shows a plurality of selectable user interface objects,including “route 1” affordance 631 b and “route 2” affordance 632 b,corresponding to routes 631 a and 631 b, respectively, from currentlocation 608 of user device 100 to the dry cleaners represented by pins614 a and 614 b. Also, in FIG. 6D, user interface 604 of system 540displays route 616 corresponding to highlighted route 631 a in userinterface 602 from current location 608 of user device 100 to selectedthe dry cleaner represented by pin 614 a.

In some embodiments, the plurality of selectable objects correspond to(714) a plurality of content items that can be played (or presented)with the device (e.g., the plurality of selectable objects are songs,playlists, audio books, radio stations, or the like), and the selectedobject corresponds to a currently selected content item. For example, arespective song in a list of songs is displayed as an automaticallyselected song on a user interface of touch screen 112 of device 100based at least in part on the amount of plays of the respective song,the ordinal position of the respective song in an album, the last playedsong, and other factors. In this example, the respective automaticallyselected song is displayed as being currently played on a user interfaceof display 546-1.

In some embodiments, the plurality of selectable objects correspond to(716) a plurality of applications, and the selected object correspondsto a currently selected application.

In some embodiments, the second display is (718) a display coupled to asecond electronic device that is different from the first electronicdevice (e.g., in place of a native GUI of the second electronic device).FIGS. 6A-6V, for example, show display 546-1 (e.g., the second display)coupled to system 540 (e.g., the second electronic device) that isdifferent (and separate) from device 100.

In some embodiments, the second electronic device controls (720) anm-vehicle entertainment system with a native graphical user interface,and the second user interface is displayed on the second display insteadof at least a portion of the native graphical user interface of thesecond electronic device (e.g., the second user interface is generatedby an application running on the first electronic device and isdisplayed instead of some or all of the native graphical user interfaceof the in-vehicle entertainment system). In FIGS. 6A-6V, for example,system 540 controls an in-vehicle entertainment system including display546-1. For example, user interface 604 in FIG. 6A, including climatecontrols for a vehicle, is the native graphical user interface of thein-vehicle entertainment system. FIGS. 6B-6V, for example, show userinterface 604 including a map displayed on display 546-1 in place of thenative graphical user interface (e.g., climate controls) as shown inFIG. 6A.

In some embodiments, the first electronic device receives (722)information that corresponds to a respective input from a control of thein-vehicle entertainment system (e.g., a tap or swipe gesture on atouch-sensitive surface associated with the second display, a buttonpress operation for a button associated with the second display and/or aknob turn operation for a knob associated with the second display). FIG.6U, for example, shows system 540 detecting user touch input 672 over“start directions” affordance 672 in user interface 604 of display546-1. In this example, system 540 sends information to device 100indicating that user touch input 672 was detected over “startdirections” affordance 672 in user interface 604 of display 546-1.

In some embodiments, in response to receiving the information thatcorresponds to the respective input, the first electronic device updates(724) the first user interface and the second user interface inaccordance with the respective input. FIG. 6V, for example, shows device100 updating user interface 602 to display turn-by-turn directions box673 on touch screen 112 and user interface 604 to display a turn-by-turnmode on display 546-1. In some embodiments, while user interface 604 isin a turn-by-turn mode, the map displayed on display 546-1 is furtherzoomed into in comparison to when user interface 604 is not inturn-by-turn mode.

In some embodiments, the first user interface and the second userinterface are both generated (726) by a same application running on thefirst electronic device (e.g., an application running on a smart phonegenerates a user interface for the phone and a user interface fordisplay on a display of an in-vehicle entertainment system of avehicle). FIG. 6A, for example, shows user touch input 606 selectingmaps application 436 in user interface 602. FIGS. 6B-6V, for example,show maps application 436 running on device 100 and generating both userinterface 602 on touch screen 112 (e.g., the first user interface) anduser interface 604 on display 546-1 (e.g., the second user interface).

While the first object is displayed (728) as the selected object in thesecond user interface, the first electronic device detects (730) a firstinput (e.g., a tap or swipe gesture on the first touch-sensitive surfaceof the first electronic device) from a user that corresponds to arequest to display information about a second object in the plurality ofselectable objects in the first user interface (e.g., without selectingthe second object as the selected object). FIG. 6L, for example, showsdevice 100 detecting user touch input 643 over the user interface object(e.g., pin) corresponding to the dry cleaner represented by pin 614 b onthe map displayed in user interface 602 including the dry cleanersrepresented by pins 614 a, 614 b, 614 c, 614 e, and 614 f. FIG. 6L, forexample, also shows user system 540 displaying turn-by-turn directionsmode including route 616 from marker 636 to the dry cleaner representedby pin 614 a in user interface 604 of display 546-1 while device 100detects user touch

While the first object is displayed (728) as the selected object in thesecond user interface, in response to detecting the first input, thefirst electronic device updates (732) the first user interface on thefirst display in accordance with the first input to display respectiveinformation about the second object while display of the first object asthe selected object in the second user interface is maintained. FIG. 6M,for example, shows device 100 updating user interface 602 to displayinformation box 644 corresponding to the dry cleaner represented by pin614 b in response to detecting user touch input 643 over the userinterface object (e.g., pin) corresponding to the dry cleanerrepresented by pin 614 b in FIG. 6L. While user interface 602 is updatedin FIG. 6M, user interface 604 is maintained on display 546-1 in FIG. 6Mas shown prior to detecting user touch input 643 in FIG. 6L.

In some embodiments, the first user interface is updated (734) inresponse to detecting the first input without providing, to the seconddisplay, information that enables the second user interface on thesecond display to be updated to display the respective information aboutthe second object in the second user interface (e.g., the firstelectronic device does not send the respective information to the secondelectronic device or the second display in response to the first input).FIG. 6M, for example, shows device 100 updating user interface 602 ontouch screen 112 in response to detecting user touch input 643 in FIG.6L without providing information to display 546-1 (or system 540) thatenables user interface 604 on display 546-1 to be updated. While userinterface 602 is updated in FIG. 6M, user interface 604 is maintained ondisplay 546-1 in FIG. 6M as shown prior to detecting user touch input643 in FIG. 6L.

In some embodiments, updating the first user interface on the firstdisplay in accordance with the first input to display respectiveinformation about the second object while display of the first object asthe selected object in the second user interface is maintained includes(736) updating the first user interface on the first display inaccordance with the first input to display respective information aboutthe second object while the entire second user interface is maintainedon the second display as it was displayed immediately prior to detectingthe first input (e.g., the second user interface is not updated inresponse to the first update). FIG. 6M, for example, shows device 100updating user interface 602 on touch screen 112 to display informationbox 644 corresponding to the dry cleaner represented by pin 614 b inresponse to detecting user touch input 643 in FIG. 6L. While userinterface 602 is updated in FIG. 6M, user interface 604 is maintained ondisplay 546-1 in FIG. 6M as shown prior to detecting user touch input643 in FIG. 6L.

While the first object is displayed (728) as the selected object in thesecond user interface, after updating the first user interface inaccordance with the first input, the first electronic device detects(738) a second input from a user that corresponds to a request to selectthe second object as the selected object. FIG. 6Q, for example, showsdevice 100 detecting user touch input 661 corresponding to a request todisplay turn-by-turn directions for route 659 a from current location608 of device 100 to the dry cleaner represented by pin 614 b (e.g.,Mary Ann's Cleaners).

In response to detecting (740) the second input, the first electronicdevice updates (742) the first user interface on the first display inaccordance with the second input to display the second object as theselected object. FIG. 6R, for example, shows, device 100 updating userinterface 602 to display turn-by-turn directions box 662 from currentlocation 608 of device 100 to the dry cleaner represented by pin 614 b(e.g., Mary Ann's Cleaners) in response to detecting user touch input661 in FIG. 6Q.

In response to detecting (740) the second input, the first electronicdevice provides (744), to the second display, information that enablesthe second user interface on the second display to be updated to displaythe second object as the selected object instead of the first object. Inresponse to detecting user touch input 661 in FIG. 6Q, device 100 sendssystem 540 information to enable system 540 to update user interface 604on display 546-1. FIG. 6R, for example, shows updated user interface 604where turn-by-turn directions mode (e.g., from current location 608 ofdevice 100 to the dry cleaner represented by pin 614 b) is displayed inuser interface 604 of display 546-1 including marker 664 indicating thecurrent location of device 100, route 659 a to the dry cleanerrepresented by pin 614 b (e.g., Mary Ann's Cleaners), and turn-by-turndirections box 663 indicating the user's first direction (or turn) onroute 659 a.

In some embodiments, after providing the information that enables (746)the second user interface on the second display to be updated to displaythe second object as the selected object instead of the first object,the first electronic device enters (748) a display synchronization mode(e.g., entering a playlist play mode or driving directions mode). FIG.6R, for example, shows device 100 displaying turn-by-turn directions box662 from current location 608 of device 100 to the dry cleanerrepresented by pin 614 b in user interface 602 of touch screen 112(e.g., a display synchronization mode). In some embodiments, while inthe display synchronization mode (750): the first electronic deviceperiodically updates (752) the first user interface over time (e.g.,updating displayed cover art as the first electronic device playsthrough a sequence of songs in a playlist or updating a displayed map toindicate progress of a vehicle moving along a navigation route). Forexample, while device 100 displays turn-by-turn directions box 662 asshown in FIG. 6R, device 100 periodically updates user interface 602 toshow the updated next direction (or turn) on route 659 a and the updatedmileage and time remaining in turn-by-turn directions box 662 as device100 approaches the destination (e.g., the dry cleaner represented by pin614 b corresponding to Mary Ann's Cleaners). In some embodiments, whilein the display synchronization mode (750): the first electronic deviceprovides (754) information that enables the second user interface on thesecond display to be synchronized with the first user interface as thefirst user interface is updated over time (e.g., providing updated coverart or map images to the display as the first electronic device playsthrough the playlist or the vehicle moves along the navigation route).For example, while device 100 displays turn-by-turn directions box 662as shown in FIG. 6R, device 100 provides information to system 540 thatenables system 540 to display updated user interface 604 including theupdated next direction (or turn) on route 659 a, the updated mileage andtime remaining in turn-by-turn directions box 663 and marker 664 (e.g.,the current location of device 100) as device 100 approaches thedestination (e.g., the dry cleaner represented by pin 614 bcorresponding to Mary Ann's Cleaners).

In some embodiments, prior to detecting the first input, the first userinterface is synchronized (756) with the second user interface (e.g.,the first object is displayed in both the first user interface and thesecond user interface as the selected object); after responding to thefirst input and prior to detecting the second input, the first userinterface is not synchronized with the second user interface (e.g., asecond object is displayed as the selected object in the first userinterface while the second object remains displayed as the selectedobject in the second user interface); and after responding to the secondinput, the first user interface is synchronized with the second userinterface (e.g., the second object is displayed as the selected objectin both the first user interface and the second user interface).

In FIG. 6H, first user interface 602 and second user interface 604 aresynchronized. FIG. 6H, for example, shows user interface 602 on touchscreen 112 displaying turn-by-turn directions box 634 indicating theuser's first direction (or turn) on route 631 a from current location608 of device 100 to the dry cleaner represented by pin 614 a (e.g., theselected first object) and the name of the selected first object, ordestination, (e.g., ABC Cleaners). FIG. 6H, for example, also shows userinterface 604 on display 546-1 displaying a turn-by-turn directions modewith route 616 from the current location 608 of device 100 to the drycleaner represented by pin 614 a (e.g., the first selected object).

In FIG. 6M, first user interface 602 and second user interface 604 arenot synchronized. FIG. 6M, for example, shows user interface 602 ontouch screen 112 displaying information box 644 corresponding to the drycleaner represented by pin 614 b (e.g., the selected second object).FIG. 6M, for example, also shows user interface 604 on display 546-1displaying route 616 from current location 608 of device 100 to the drycleaner represented by pin 614 a (e.g., the selected first object).

In FIG. 6R, first user interface 602 and second user interface 604 aresynchronized. FIG. 6R, for example, shows user interface 602 on touchscreen 112 displaying turn-by-turn directions box 662 indicating theuser's first direction (or turn) on route 659 a from current location608 of device 100 to the dry cleaner represented by pin 614 b (e.g., theselected second object) and the name of the selected second object, ordestination, (e.g., Mary Ann's Cleaners). FIG. 6R, for example, alsoshows user interface 604 on display 546-1 displaying a turn-by-turndirections mode with route 659 a from current location 608 of device 100to the dry cleaner represented by pin 614 b (e.g., the selected secondobject).

Thus, as described above, the user interface displayed on touch screendisplay 112 and display 546-1 are intermittently synchronized.Intermittently synchronizing the user interfaces displayed on touchscreen display 112 and display 546-1 enables a passenger in a vehicle tobrowse through information displayed on touch screen display 112 (e.g.,investigating different candidate destinations including contactinformation, reviews, descriptions, etc.) without the user interfacethat is displayed on the driver-visible display (e.g., display 546-1)updating constantly in response to the activity of the passenger.However, once the passenger has committed to an operation (e.g.,selected a destination) in the user interface displayed on touch screendisplay 112, the user interfaces on the displays are synchronized, sothat the driver can drive to the selected destination and the user canhelp to navigate to the selected destination. Similarly, if the driverselects a destination in the user interface that is displayed on thedriver-visible display (e.g., display 546-1), the user interfacedisplayed on touch screen display 112 is updated to reflect the driver'sselection, so that the passenger can help the driver navigate to theselected destination. The intermittent synchronization of userinterfaces described above is an improvement over a situation where theuser interfaces displayed on two displays are continuously synchronized(e.g., because the passenger is able to view additional informationwithout repeatedly changing the information displayed to the driver).Additionally, the intermittent synchronization of user interfacesdescribe above is an improvement over a situation where the userinterfaces displayed on two displays are never synchronized (e.g.,because the passenger does not need to take the additional step ofupdating a destination address in a car navigation system after lookingup the address on device 100).

It should be understood that the particular order in which theoperations in FIGS. 7A-7D have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 800 and 900) are also applicable in an analogous manner tomethod 700 described above with respect to FIGS. 7A-7D. For example, thecontacts, gestures, user interface objects described above withreference to method 700 optionally have one or more of thecharacteristics of the contacts, gestures, user interface objectsdescribed herein with reference to other methods described herein (e.g.,methods 800 and 900). For brevity, these details are not repeated here.

FIGS. 8A-8B are flow diagrams illustrating a method 800 of synchronizingtwo or more displays in accordance with some embodiments. Method 800 isperformed at a portable electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) that is in communicationwith a vehicle display of a vehicle. The portable electronic deviceincludes a portable-device display and a touch-sensitive surface. Insome embodiments, the portable-device display is a touch screen displayand the touch-sensitive surface is on the portable-device. In someembodiments, the portable-device is separate from the touch-sensitivesurface. Some operations in method 800 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, method 800 provides an intuitive way to synchronizetwo or more displays. The method reduces the cognitive burden on a userwhen using two or more displays, thereby creating a more efficienthuman-machine interface. For battery-operated electronic devices,enabling a user to synchronize two or more displays faster and moreefficiently conserves power and increases the time between batterycharges.

The portable electronic device obtains (802) a set of map search resultsthat includes a plurality of candidate destinations. FIG. 6C, forexample, shows a user search query (e.g., dry cleaning) displayed insearch box 609 in user interface 602 of touch screen 112. In response tothe search query, device 100 obtains a set of map search results thatincludes a plurality of candidate destinations by searching a memorylocal to device 100, a memory external to device 100, the Internet, or acombination thereof.

The portable electronic device displays (804) a portable-devicenavigation interface on the portable-device display, where theportable-device navigation interface enables selection of a destinationfrom the plurality of candidate destinations (e.g., search results thatcorrespond to a previously performed search operation). FIG. 6D, forexample, shows a portable-device navigation interface (e.g., userinterface 602) corresponding to the search query “dry cleaning” inputinto search query box 609 in FIG. 6C displayed on touch screen 112. InFIG. 6D, user interface 602 includes selectable user interface objects(e.g., pins), or affordances, corresponding to the dry cleanersrepresented by pins 614 a and 614 b nearby current location 608 ofdevice 100.

The portable electronic device sends (806) information to the vehicledisplay that enables the vehicle display to display a vehicle navigationinterface, where a first destination of the plurality of candidatedestinations is a selected destination in the vehicle navigationinterface. FIG. 6D, for example, shows a vehicle navigation interface(e.g., user interface 604) displayed on display 546-1 of system 540. InFIG. 6D, the dry cleaner represented by pin 614 a (e.g., ABC Cleaners)is displayed as the selected destination in user interface 604 ofdisplay 546-1 and route 616 from current location 608 of device 100 tothe dry cleaner represented by pin 614 a is also displayed in userinterface 604 of display 546-1. In some embodiments, display 546-1 is atouch screen display. In some embodiments, display 546-1 is a primarydisplay of a plurality of displays associated with system 540. In someembodiments, display 546-1 is implemented in the dashboard of thevehicle and is visually accessible to the driver and/or passenger of thevehicle.

While the first destination is (808) the selected destination in thevehicle navigation interface, the portable electronic device detects(810) a first input (e.g., a tap or swipe gesture on a touch-sensitivesurface of the first electronic device) from a user that corresponds toa request to display information about one or more candidatedestinations in the plurality of candidate destinations other than thefirst destination (e.g., without selecting the second object as theselected object). FIG. 6L, for example, shows device 100 detecting usertouch input 643 over the user interface object (e.g., pin) correspondingto the dry cleaner represented by pin 614 b (e.g., Mary Ann's Cleaners)on the map displayed in user interface 602. In FIG. 6L, the mapdisplayed in user interface includes the dry cleaners represented bypins 614 a, 614 b, 614 c, 614 e, and 614 f In FIG. 6L, for example, thedry cleaner represented by pin 614 a (e.g., ABC Cleaners) is displayedas the selected destination in user interface 604 of display 546-1.

While the first destination is (808) the selected destination in thevehicle navigation interface, in response to detecting the first input,the portable electronic device updates (812) the portable-devicenavigation interface on the portable-device display in accordance withthe first input without the vehicle navigation interface on the vehicledisplay being updated. FIG. 6M, for example, shows device 100 updatinguser interface 602 to display information box 644 corresponding to thedry cleaner represented by pin 614 b in response to detecting user touchinput 643 over the user interface object (e.g., pin) corresponding tothe dry cleaner represented by pin 614 b in FIG. 6L. In FIG. 6M, userinterface 602 is updated without providing information to display 546-1(or system 540) that enables user interface 604 on display 546-1 to beupdated. In FIG. 6M, for example, the dry cleaner represented by pin 614a is displayed as the selected destination in user interface 604 ofdisplay 546-1.

While the first destination is (808) the selected destination in thevehicle navigation interface, after updating the portable-devicenavigation interface in accordance with the first input, the portableelectronic device detects (814) a second input from a user thatcorresponds to a request to select a second destination in the pluralityof candidate destinations as the selected destination. FIG. 6Q, forexample, shows device 100 detecting user touch input 661 correspondingto a request to display turn-by-turn directions for route 659 a fromcurrent location 608 of device 100 to the dry cleaner represented by pin614 b (e.g., Mary Ann's Cleaners).

In response to detecting (816) the second input, the portable electronicdevice updates (818) the portable-device navigation interface on theportable-device display in accordance with the second input to displaythe second destination as the selected destination. FIG. 6R, forexample, shows, device 100 updating user interface 602 to displayturn-by-turn directions box 662 with directions to the dry cleanerrepresented by pin 614 b (e.g., Mary Ann's Cleaners) in response todetecting user touch input 661 in FIG. 6Q.

In response to detecting (816) the second input, the portable electronicdevice sends (820) information to the vehicle display that enables thevehicle display to update the vehicle navigation interface in accordancewith the second input to display the second destination as the selecteddestination. In response to detecting user touch input 661 in FIG. 6Q,device 100 sends system 540 information to enable system 540 to updateuser interface 604 on display 546-1. FIG. 6R, for example, shows updateduser interface 604 where turn-by-turn directions mode is displayed inuser interface 604 of display 546-1 including marker 664 indicating thecurrent location of device 100, route 659 a from current location 608 ofdevice 100 to the dry cleaner represented by pin 614 b (e.g., Mary Ann'sCleaners), and turn-by-turn directions box 663 indicating the user'sfirst direction (or turn) on route 659 a.

It should be understood that the particular order in which theoperations in FIGS. 8A-8B have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700 and 900) are also applicable in an analogous manner tomethod 800 described above with respect to FIGS. 8A-8B. For example, thecontacts, gestures, user interface objects described above withreference to method 800 optionally have one or more of thecharacteristics of the contacts, gestures, user interface objectsdescribed herein with reference to other methods described herein (e.g.,methods 700 and 900). For brevity, these details are not repeated here.

FIGS. 9A-9C are flow diagrams illustrating a method 900 of sendingupdate information to an affected display in accordance with someembodiments. Method 900 is performed at an electronic device (e.g.,device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) thatis in communication with a plurality of displays that include a firstdisplay and a second display. In some embodiments, the electronicdevice, optionally, includes a display and a touch-sensitive surface. Insome embodiments, the display is a touch screen display and thetouch-sensitive surface is on the electronic device. In someembodiments, the electronic device is separate from the touch-sensitivesurface. Some operations in method 900 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, the method 900 provides an efficient way to sendupdate information to an affected display.

An electronic device that is in communication with a plurality ofdisplays that include a first display and a second display receives(902) first input information that is indicative of a first inputdetected by a first input source of a plurality of input sources, wherethe first input information includes: a first (unique) identifier forthe first input source; and a first input description that describes thefirst input. For example, the first input source description is rawinput data such as contact locations and movement amounts/directionsdetected on a touch-sensitive surface and/or gesture data describing atype of gesture that was performed on the touch-sensitive surface. Insome embodiments, the device is in communication with a plurality ofdifferent input sources (e.g., one or more buttons, knobs, jog dials,and/or touch-sensitive surfaces) where a respective input source ismapped to work in conjunction with a particular display. In someembodiments, as described in greater detail below with reference to FIG.6DD-6EE, the mapping is, optionally, updated so that the mapping of arespective input source is changed from being mapped to the firstdisplay to being mapped to the second display.

FIGS. 6W-6FF, for example, show device 100 in communication with display546-1 and 546-2. For example, display 546-1 (e.g., a primary display)and 546-2 (e.g., an auxiliary display) are associated with system 540which is implemented in a vehicle. For example, jog dial 675 isassociated with system 540 and, when activated, causes the device tocontrol one or both of display 546-1 and display 546-2. FIG. 6X, forexample, shows jog dial 675 detecting turn 681 (e.g., an approximately90 degree clockwise turn). In response to detecting turn 681, jog dial675 (or system 540) sends input information indicative of turn 681 todevice 100. The input information includes an identifier associated withjog dial 675 (e.g., a unique identifier associated with jog dial 675)and input description information describing turn 681. For example, theinput description information includes raw data describing turn 681 suchas the magnitude (90 degrees) and direction (clockwise) of the turn.

The device selects (904) a first affected display from the plurality ofdisplays based on the first identifier and an input-source mapping thatmaps input sources to corresponding displays. For example, in responseto receiving input information corresponding to turn 681 in FIG. 6X fromjog dial 675, device 100 selects (or determines) an affected display bycorrelating the identifier (e.g., identifying the input source as jogdial 675) included in the input information with a display (e.g.,display 546-1) based on an input-source mapping that maps input sourcesto displays.

In some embodiments, selecting the first affected display includes(906): in accordance with a determination that the first input source isassigned to the first display in the input-source mapping, selecting thefirst display as the first affected display that is affected by thefirst input; and in accordance with a determination that the first inputsource is assigned to the second display, different from the firstdisplay, in the input-source mapping, selecting the second display asthe first affected display that is affected by the first input. Forexample, in response to receiving input information corresponding to thepinch gesture in FIG. 6W from the touch-sensitive surface associatedwith display 546-1, device 100 selects (or determines) an affecteddisplay by correlating the identifier (e.g., identifying the inputsource as the touch-sensitive surface associated with display 546-1)included in the input information with a display (e.g., display 546-1)based on the input-source mapping that maps input sources to displays.In another example, in response to receiving input informationcorresponding to the upward swipe gesture in FIG. 6EE from thetouch-sensitive surface associated with display 546-2, device 100selects (or determines) an affected display by correlating theidentifier (e.g., identifying the input source as the touch-sensitivesurface associated with display 546-2) included in the input informationwith a display (e.g., display 546-2) based on the input-source mappingthat maps input sources to displays.

In some embodiments, after selecting the first affected display, thedevice (908): determines a respective state of a user interfacedisplayed on the first affected display (e.g., a user interfacedisplayed on the first affected display immediately prior to when thefirst input information was received); and generates the updateinformation based on the first input description and the respectivestate of the user interface displayed on the first affected display. Forexample, in response to receiving input information corresponding toturn 681 in FIG. 6X from jog dial 675, device 100 selects (ordetermines) an affected display by correlating the identifier (e.g.,identifying the input source as jog dial 675) included in the inputinformation with a display (e.g., display 546-1) based on aninput-source mapping that maps input sources to displays. In thisexample, after determining that the turn event detected in FIG. 6X isassociated with display 546-1, device 100 also determines the displaystate of display 546-1 shown in FIG. 6X (e.g., user interface 604 is ina search results or destination selection mode). In this example, device100 generates the update information (e.g., the updated user interfacedisplayed on display 546-1 in FIG. 6Y) based on the input descriptioninformation shown in FIG. 6X (e.g., an approximately 90 degree clockwiseturn) and the display state of display 546-1 (e.g., user interface 604is in a search results or destination selection mode).

In some embodiments, in accordance with a determination that therespective state of the user interface displayed on the first affecteddisplay is a first state, the update information corresponds to (910)performing a first operation for the respective state of the userinterface displayed on the first affected display (e.g., the respectivestate is displaying a “now playing” interface for playing audio and therespective operation includes adjusting a volume level of audio playbackassociated with the user interface displayed on the first affecteddisplay in accordance with an amount of rotation of a knob); and inaccordance with a determination that the respective state of the userinterface displayed on the first affected display is a second statedifferent from the first state, the update information corresponds toperforming a second operation, different from the first operation, forthe respective state of the user interface displayed on the firstaffected display (e.g., the respective state is displaying a list ofselectable items such as audio content items and the respectiveoperation includes navigating through the list of selectable items onthe first affected display in accordance with an amount of rotation of aknob). FIGS. 6Y-6Z, for example, shows display 546-1 scrollingsouth-to-north through selected search results (e.g., dry cleaners) inuser interface 604 in response to detecting turn 683 of jog dial 675 inFIG. 6Y (e.g., an approximately 180 degree counter-clockwise turn) andin accordance with the display state of user interface 604 in FIG. 6Y(e.g., a search results or destination selection mode). FIGS. 6AA-6BB,for example, show display 546-1 zooming out a turn-by-turn directionsmode in user interface 604 in response to detecting turn 686 of jog dial675 in FIG. 6AA (e.g., an approximately 90 degree counter-clockwiseturn) and in accordance with the display state of user interface 604 inFIG. 6AA (e.g., a turn-by-turn directions mode).

In some embodiments, prior to receiving the first input information, therespective user interface has a prior state; and the device updates(912) the user interface to an updated state that is different from theprior state based on the first input and the prior state of therespective user interface (e.g., in response to a swipe gesture on atouch-sensitive surface or a rotation of a knob, a map user interface isscrolled in accordance with a magnitude and direction of the swipegesture or the magnitude of the rotation of the knob). FIGS. 6EE-6FF,for example, show display 546-2 scrolling up a list of songs 677 in userinterface 676 in response to detecting an upward swipe gesture with usertouch input 689 on display 546-2 in FIG. 6EE and in accordance with thedisplay state of user interface 676 in FIG. 6EE (e.g., an album songlist mode).

In some embodiments, prior to sending the update information to thefirst affected display, the device generates (914) the updateinformation based on the first input information, where: in accordancewith a determination that the first input description describes firstinput properties, the device generates first update information; and inaccordance with a determination that the first input descriptiondescribes second input properties different from the first inputproperties, the device generates second update information differentfrom the first update information. For example, when the first inputinformation corresponds to rotation of a knob while a list is displayedon the first affected display, if the first input description indicatesthat the first input includes clockwise rotation of a knob, the devicescrolls a list downward on the affected display; in contrast, if thefirst input description indicates that the first input includescounter-clockwise rotation of the knob, the device scrolls the listupward on the affected display.

In another example, when the search results or a destination selectionmode is displayed, a 90 degree turn of jog dial 675 selects a nextsearch result, a clockwise turn scrolls the search resultsnorth-to-south, and a counter-clockwise turn scrolls the search resultssouth-to-north. FIGS. 6X-6Y, for example, show display 546-1 scrollingnorth-to-south through selected search results (e.g., dry cleaners) inuser interface 604 in response to detecting turn 681 of jog dial 675 inFIG. 6X (e.g., an approximately 90 degree clockwise turn). In contrast,FIGS. 6Y-6Z, for example, shows display 546-1 scrolling south-to-norththrough selected search results (e.g., dry cleaners) in user interface604 in response to detecting turn 683 of jog dial 675 in FIG. 6Y (e.g.,an approximately 180 degree counter-clockwise turn).

The device sends (916), to the first affected display, updateinformation that enables the first affected display to be updated inaccordance with the first input. For example, in response to receivinginput information corresponding to turn 681 in FIG. 6X from jog dial675, device 100 selects display 546-1 as the affected display bycorrelating the identifier (e.g., identifying the input source as jogdial 675) included in the input information with display 546-1 based onthe input-source mapping. After selecting display as the affecteddisplay, device 100 sends affected display 546-1 update information thatenables affected display 546-1 to be updated.

In some embodiments, the update information includes (918) informationcorresponding to the first input (e.g., raw input data such as contactlocations and movement amounts/directions detected on a touch-sensitivesurface and/or gesture data describing a type of gesture that wasperformed on the touch-sensitive surface). In some embodiments, theupdate information includes the first input description. In someembodiments, the update information is generated based on the firstinput description (e.g., the first input description is raw touch inputdata and the update information includes a gesture that corresponds tothe raw touch input data).

In some embodiments, the update information includes (920) an updateduser interface for display at the first affected display (e.g., an imagefor display on the first display that includes a plurality of userinterface objects). After selecting display 546-1 as the affecteddisplay corresponding to turn 681 in FIG. 6X, device I 00 sends affecteddisplay 546-1 update information that enables affected display 546-1 tobe updated in accordance with the magnitude (90 degrees) and direction(clockwise) of turn 681 of jog dial 675 in FIG. 6X. For example, theupdate information includes an updated user interface that scrolls thesearch results (e.g., dry cleaners) so that the next dry cleaner south(e.g., Suzie's Cleaners corresponding to the dry cleaner represented bypin 614 d) from ABC Cleaners corresponding to the dry cleanerrepresented by pin 614 a is displayed as the selected search result inuser interface 604 in FIG. 6Y.

In some embodiments, the device generates (922) user interfaces for twoor more displays of the plurality of displays and provides respectiveuser interfaces to corresponding displays. For example, device 100 sendsimages that are representative of a first map/navigation user interfacefor display on a first display (e.g., primary display 546-1 or adashboard navigation display) of a vehicle information display system(e.g., system 540), such as a vehicle entertainment or navigationsystem, and generates a second, different, map/navigation user interfacefor a second, different, display that is structurally integrated withthe device (e.g., touch-screen 112 of device 100 or another portableelectronic device). In some embodiments, the device sends images thatare representative of a different user interface for display on a thirddisplay in the vehicle (e.g., auxiliary display 546-2 or a rear-seatentertainment display) of a vehicle information display system (e.g.,system 540).

In some embodiments, after sending the update information that enablesthe first affected display to be updated in accordance with the firstinput (924), the device receives (926) second input information that isindicative of a second input detected by a second input source of theplurality of input sources distinct from the first input source, wherethe second input information includes: a second (unique) identifier forthe second input source; and a second input description that describesthe second input. For example, the second input description is raw inputdata such as contact locations and movement amounts/directions detectedon a touch-sensitive surface and/or gesture data describing a type ofgesture that was performed on the touch-sensitive surface. Afterselecting display 546-1 as the first affected display corresponding toturn 681 in FIG. 6X, device 100 sends first affected display 546-1update information that enables first affected display 546-1 to beupdated as shown in FIG. 6Y. Subsequently, FIG. 6EE, for example, showsthe touch-sensitive surface associated with display 546-2 detecting anupward swipe gesture with user touch input 689. In response to detectingthe upward swipe gesture, the touch-sensitive surface associated withdisplay 546-2 (or system 540) sends input information indicative of usertouch input 689 (or the upward swipe gesture) to device 100. The inputinformation includes an identifier associated with the touch-sensitivesurface associated with display 546-2 (e.g., a unique identifierassociated with the touch-sensitive surface associated with display546-2) and input description information describing user touch input 689(or the upward swipe gesture).

In some embodiments, after sending the update information that enablesthe first affected display to be updated in accordance with the firstinput (924), the device selects (928) a second affected display from theplurality of displays based on the second identifier and theinput-source mapping. In response to receiving input informationcorresponding to the upward swipe gesture in FIG. 6EE from thetouch-sensitive surface associated with display 546-2, device 100selects display 546-2 as the second affected display by correlating theidentifier (e.g., identifying the input source as the touch-sensitivesurface associated with display 546-2) included in the input informationwith a display (e.g., display 546-2) based on the input-source mappingthat maps input sources to displays.

In some embodiments, after sending the update information that enablesthe first affected display to be updated in accordance with the firstinput (924), the device sends (930), to the second affected display,update information that enables the second affected display to beupdated in accordance with the second input. In some embodiments (e.g.,where the first input source and the second input source are both mappedto a same display), the first affected display is the same as the secondaffected display. In some embodiments (e.g., where the first inputsource and the second input source are mapped to different displays),the first affected display is different from the second affecteddisplay. After selecting display 546-2 as the second affected display,device 100 sends second affected display 546-2 update information thatenables affected display 546-2 to be updated. For example, in FIG. 6FF,the update information includes an updated user interface that enableddisplay 546-2 to display list 677 scrolled upward in user interface 676.

In some embodiments, the device detects (932) a change in availabilityof a respective display of the plurality of displays, and in response todetecting the change in availability of the respective display, thedevice updates the input-source mapping to show the change inavailability of the respective display. In some embodiments, the changein availability of the respective display includes a computer system(e.g., a vehicle information display system such as a navigation orentertainment system) that is different from the electronic devicetaking control of the respective display. In some embodiments, thechange in availability of the respective display includes a computersystem that is different from the electronic device giving control ofthe respective display to (or back to) the electronic device (e.g.,while the vehicle is backing up, a vehicle information display systemdisplays a video feed from a back-up camera on a display of the vehicleinformation display system and after the vehicle has ceased to back up,the vehicle information display system enables the electronic device toagain display a user interface provided by the electronic device on thedisplay of the vehicle information display system).

FIGS. 6W-6FF, for example, show display 546-1 and display 546-2associated with system 540 that is implemented in a vehicle. While thevehicle is in reverse, FIG. 6CC, for example, shows display 546-1displaying a vehicle backup mode including a video feed from backupcamera in user interface 604 and display 546-2 displaying a vehiclebackup mode including a video feed from the backup camera in userinterface 676. While the vehicle is in reverse, vehicle backup modesupersedes all update information received by displays 546-1 and 546-2from device 100.

In some embodiments, while a respective input source is assigned to thefirst display, the device detects (934) a change in display assignmentfor a respective input source of the plurality of input sources from thefirst display to the second display, and in response to detecting thechange in display assignment for the respective input source, the deviceupdates the input-source mapping to show the change in displayassignment for the respective input source, so that input informationthat is indicative of inputs associated with the respective input sourceis used to update a user interface displayed on the second displayinstead of being used to update a user interface displayed on the firstdisplay. For example, a passenger in a vehicle switches from using afirst knob to control a user interface in a primary display of a vehicleinformation display system to using the first knob to control a userinterface in an auxiliary display of the vehicle information displaysystem (e.g., a rear-seat entertainment display) and input informationthat includes an identifier for the first knob is used to update a userinterface displayed on the auxiliary display instead of being used toupdate a user interface displayed on the primary display.

In FIGS. 6W-6CC, jog dial 675, when activated, causes the device tocontrol display 546-1. Thus, in FIGS. 6W-6CC, jog dial 675 is associatedwith display 546-1 in the input-source to display mapping. For example,FIGS. 6AA-6BB show display 546-1 zooming out a turn-by-turn directionsmode in user interface 604 in response to detecting turn 686 of jog dial675 (e.g., an approximately 90 degree counter-clockwise turn) in FIG.6AA in accordance with a determination that jog dial 675 is mapped todisplay 546-1.

In contrast, in FIGS. 6DD-6EE, jog dial 675, when activated, causes thedevice to control display 546-2. Thus, in FIGS. 6DD-6EE, jog dial 675 isassociated with display 546-2 in the changed input-source to displaymapping. In another example, FIGS. 6DD-6EE show display 546-2 scrollingdown list 677 in user interface 676 in response to detecting turn 688 ofjog dial 675 (e.g., an approximately 90 degree clockwise turn) in FIG.6DD in accordance with a determination that jog dial 675 is mapped todisplay 546-2.

It should be understood that the particular order in which theoperations in FIGS. 9A-9C have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700 and 800) are also applicable in an analogous manner tomethod 900 described above with respect to FIGS. 9A-9C. For example, thecontacts, gestures, user interface objects described above withreference to method 900 optionally have one or more of thecharacteristics of the contacts, gestures, user interface objectsdescribed herein with reference to other methods described herein (e.g.,methods 700 and 800). For brevity, these details are not repeated here.

In accordance with some embodiments, FIG. 10 shows a functional blockdiagram of a first electronic device 1000 configured in accordance withthe principles of the various described embodiments. The functionalblocks of the device are, optionally, implemented by hardware, software,or a combination of hardware and software to carry out the principles ofthe various described embodiments. It is understood by persons of skillin the art that the functional blocks described in FIG. 10 are,optionally, combined or separated into sub-blocks to implement theprinciples of the various described embodiments. Therefore, thedescription herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 10, a first electronic device 1000 includes a firstdisplay unit 1002 configured to display to display a first userinterface, where: the first user interface enables selection between aplurality of selectable objects; the first user interface corresponds toa second user interface displayed on a second display unit differentfrom the first display unit; and a first object from the plurality ofselectable objects is displayed as a selected object in the second userinterface. Optionally, first electronic device 1000 also includes acommunications interface unit 1004 configured to communicate with asecond electronic device and a first touch-sensitive surface unit 1006configured to receive one or more touch inputs. First electronic device1000 further includes a processing unit 1008 coupled to first displayunit 1002, and, optionally, coupled to communications interface unit1004 and first touch-sensitive surface unit 1006. In some embodiments,processing unit 1008 includes a detecting unit 1010, an updating unit1012, a providing unit 1014, a synchronization unit 1016, and areceiving unit 1018.

While the first object is displayed as the selected object in the seconduser interface, processing unit 1008 is configured to: detect (e.g.,with detecting unit 1010) a first input from a user that corresponds toa request to enable display of information about a second object in theplurality of selectable objects in the first user interface; in responseto detecting the first input, update (e.g., with updating unit 1012) thefirst user interface on first display unit 1002 in accordance with thefirst input to enable display of respective information about the secondobject while display of the first object as the selected object in thesecond user interface is maintained; and after updating the first userinterface in accordance with the first input, detect (e.g., withdetecting unit 1010) a second input from a user that corresponds to arequest to select the second object as the selected object. In responseto detecting the second input, processing unit 1008 is furtherconfigured to: update (e.g., with updating unit 1012) the first userinterface on first display unit 1002 in accordance with the second inputto enable display of the second object as the selected object; andprovide (e.g., with providing unit 1014), to the second display unit,information that enables the second user interface on the second displayunit to be updated to enable display of the second object as theselected object instead of the first object.

In some embodiments, the first user interface is updated in response todetecting the first input without providing, to the second display unit,information that enables the second user interface on the second displayunit to be updated to enable display of the respective information aboutthe second object in the second user interface.

In some embodiments, updating the first user interface on first displayunit 1002 in accordance with the first input to enable display ofrespective information about the second object while display of thefirst object as the selected object in the second user interface ismaintained includes updating the first user interface on first displayunit 1002 in accordance with the first input to enable display ofrespective information about the second object while the entire seconduser interface is maintained on the second display unit as it wasdisplayed immediately prior to detecting the first input.

In some embodiments, the plurality of selectable objects correspond to aplurality of map locations, and the selected object corresponds to acurrently selected destination.

In some embodiments, the plurality of selectable objects correspond to aplurality of navigation routes, and the selected object corresponds to acurrently selected navigation route.

In some embodiments, the plurality of selectable objects correspond to aplurality of content items that can be played with first electronicdevice 1000, and the selected object corresponds to a currently selectedcontent item.

In some embodiments, the plurality of selectable objects correspond to aplurality of applications, and the selected object corresponds to acurrently selected application.

In some embodiments, the plurality of selectable objects correspond to aplurality of search results produced in response to a search query, andthe selected object corresponds to a currently selected search result.

In some embodiments, the first object was automatically selected as theselected object based on predefined object selection criteria.

In some embodiments, prior to detecting the first input, the first userinterface is synchronized with the second user interface; afterresponding to the first input and prior to detecting the second input,the first user interface is not synchronized with the second userinterface; and after responding to the second input, the first userinterface is synchronized with the second user interface.

In some embodiments, processing unit 1008 is configured to: afterproviding the information that enables the second user interface on thesecond display unit to be updated to enable display of the second objectas the selected object instead of the first object, enter (e.g., withsynchronization unit 1016) a display synchronization mode; and while inthe display synchronization mode: periodically update (e.g., withupdating unit 1012) the first user interface over time; and provide(e.g., with providing unit 1014) information that enables the seconduser interface on the second display unit to be synchronized with thefirst user interface as the first user interface is updated over time.

In some embodiments, the second electronic device controls an in-vehicleentertainment system with a native graphical user interface, and thesecond user interface is displayed on the second display unit instead ofat least a portion of the native graphical user interface of the secondelectronic device.

In some embodiments, processing unit 1008 is configured to: receive(e.g., with receiving unit 1018) information that corresponds to arespective input from a control of the in-vehicle entertainment system;and in response to receiving the information that corresponds to therespective input, update (e.g., with updating unit 1012) the first userinterface and the second user interface in accordance with therespective input.

In accordance with some embodiments, FIG. 11 shows a functional blockdiagram of a portable electronic device 1100 configured in accordancewith the principles of the various described embodiments. The functionalblocks of the device are, optionally, implemented by hardware, software,or a combination of hardware and software to carry out the principles ofthe various described embodiments. It is understood by persons of skillin the art that the functional blocks described in FIG. 11 are,optionally, combined or separated into sub-blocks to implement theprinciples of the various described embodiments. Therefore, thedescription herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 11, a portable electronic device 1100 includes aportable device display unit 1102 configured to display aportable-device navigation interface, a communications interface unit1104 configured to communicate with a vehicle display unit of a vehicle,and, optionally, a touch-sensitive surface unit 1106 configured toreceive one or more touch inputs; and a processing unit 1108 coupled toportable-device display unit 1102, communications interface unit 1104,and, optionally, touch-sensitive surface unit 1106. In some embodiments,processing unit 1108 includes an obtaining unit 1110, a display enablingunit 1112, a sending unit 1114, a detecting unit 1116, and an updatingunit 1118.

Processing unit 1108 is configured to: obtain (e.g., with obtaining unit1110) a set of map search results that includes a plurality of candidatedestinations; enable display (e.g., with display enabling unit 1112) ofthe portable-device navigation interface on portable-device display unit1102, where the portable-device navigation interface enables selectionof a destination from the plurality of candidate destinations; and send(e.g., with sending unit 1114) information to the vehicle display unitthat enables the vehicle display unit to enable display of the vehiclenavigation interface, where a first destination of the plurality ofcandidate destinations is a selected destination in the vehiclenavigation interface. While the first destination is the selecteddestination in the vehicle navigation interface, processing unit 1108 isalso configured to: detect (e.g., with detecting unit 1116) a firstinput from a user that corresponds to a request to enable display ofinformation about one or more candidate destinations in the plurality ofcandidate destinations other than the first destination; in response todetecting the first input, update (e.g., with updating unit 1118) theportable-device navigation interface on portable-device display unit1102 in accordance with the first input without the vehicle navigationinterface on the vehicle display unit being updated; and after updatingthe portable-device navigation interface in accordance with the firstinput, detect (e.g., with detecting unit 1116) a second input from auser that corresponds to a request to select a second destination in theplurality of candidate destinations as the selected destination.

In accordance with some embodiments, FIG. 12 shows a functional blockdiagram of a portable electronic device 1200 configured in accordancewith the principles of the various described embodiments. The functionalblocks of the device are, optionally, implemented by hardware, software,or a combination of hardware and software to carry out the principles ofthe various described embodiments. It is understood by persons of skillin the art that the functional blocks described in FIG. 12 are,optionally, combined or separated into sub-blocks to implement theprinciples of the various described embodiments. Therefore, thedescription herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 12, an electronic device 1200 includes a communicationsinterface unit 1202 configured to communicate with a plurality ofdisplays that include a first display and a second display. In someembodiments, electronic device 1200 also, optionally, includes a displayunit 1204 configured to display a user interface and a touch-sensitivesurface unit 1206 configured to one or more receive touch inputs.Electronic device 1200 further includes a processing unit 1208 coupledto communications interface unit 1202, and, optionally, coupled todisplay unit 1204 and touch-sensitive surface unit 1206. In someembodiments, processing unit 1208 includes a receiving unit 1210, aselecting unit 1212, a sending unit 1214, a generating unit 1216, adetermining unit 1218, an updating unit 1220, a detecting unit 1222, anda mapping update unit 1224.

Processing unit 1208 is configured to receive (e.g., with receiving unit1210) a first input information that is indicative of a first inputdetected by a first input source of a plurality of input sources, wherethe first input information includes: a first identifier for the firstinput source; and a first input description that describes the firstinput. Processing unit 1208 is also configured to select (e.g., withselecting unit 1212) a first affected display from the plurality ofdisplays based on the first identifier and an input-source mapping thatmaps input sources to corresponding displays. Processing unit 1208 isfurther configured to send (e.g., with sending unit 1214), to the firstaffected display, update information that enables the first affecteddisplay to be updated in accordance with the first input.

In some embodiments, selecting the first affected display includes: inaccordance with a determination that the first input source is assignedto the first display in the input-source mapping, selecting (e.g., withselecting unit 1212) the first display as the first affected displaythat is affected by the first input; and in accordance with adetermination that the first input source is assigned to the seconddisplay, different from the first display, in the input-source mapping,selecting (e.g., with selecting unit 1212) the second display as thefirst affected display that is affected by the first input.

In some embodiments, the update information includes informationcorresponding to the first input.

In some embodiments, the update information includes an updated userinterface for display at the first affected display.

In some embodiments, the device generates user interfaces for two ormore displays of the plurality of displays and provides respective userinterfaces to corresponding displays.

In some embodiments, prior to sending the update information to thefirst affected display, processing unit 1208 is configured to generate(e.g., with generating unit 1216) the update information based on thefirst input information, where: in accordance with a determination thatthe first input description describes first input properties, processingunit 1208 is configured to generate (e.g., with generating unit 1216)first update information; and in accordance with a determination thatthe first input description describes second input properties differentfrom the first input properties, processing unit 1208 is configured togenerate (e.g., with generating unit 1216) second update informationdifferent from the first update information.

In some embodiments, after selecting the first affected display,processing unit 1208 is configured to: determine (e.g., with determiningunit 1218) a respective state of a user interface displayed on the firstaffected display; and generate (e.g., with generating unit 1216) theupdate information based on the first input description and therespective state of the user interface displayed on the first affecteddisplay.

In some embodiments, in accordance with a determination that therespective state of the user interface displayed on the first affecteddisplay is a first state, the update information corresponds toperforming a first operation for the respective state of the userinterface displayed on the first affected display; and in accordancewith a determination that the respective state of the user interfacedisplayed on the first affected display is a second state different fromthe first state, the update information corresponds to performing asecond operation, different from the first operation, for the respectivestate of the user interface displayed on the first affected display.

In some embodiments, prior to receiving the first input information, therespective user interface has a prior state; and processing unit 1208 isconfigured to update (e.g., with updating unit 1220) the user interfaceto an updated state that is different from the prior state based on thefirst input and the prior state of the respective user interface.

In some embodiments, processing unit 1208 is configured to: detect(e.g., with detecting unit 1222) a change in availability of arespective display of the plurality of displays; and in response todetecting the change in availability of the respective display, update(e.g., with mapping update unit 1224) the input-source mapping to showthe change in availability of the respective display.

In some embodiments, while a respective input source is assigned to thefirst display, processing unit 1208 is configured to detect (e.g., withdetecting unit 1222) a change in display assignment for a respectiveinput source of the plurality of input sources from the first display tothe second display. And, in response to detecting the change in displayassignment for the respective input source, processing unit 1208 isconfigured to update (e.g., with mapping update unit 1224) theinput-source mapping to show the change in display assignment for therespective input source, so that input information that is indicative ofinputs associated with the respective input source is used to update auser interface displayed on the second display instead of being used toupdate a user interface displayed on the first display.

In some embodiments, after sending the update information that enablesthe first affected display to be updated in accordance with the firstinput, processing unit 1208 is configured to receive (e.g., withreceiving unit 1210) second input information that is indicative of asecond input detected by a second input source of the plurality of inputsources distinct from the first input source, where the second inputinformation includes: a second identifier for the second input source;and a second input description that describes the second input.Processing unit 1208 is also configured to: select (e.g., with selectingunit 1212) a second affected display from the plurality of displaysbased on the second identifier and the input-source mapping; and send(e.g., with sending unit 1214), to the second affected display, updateinformation that enables the second affected display to be updated inaccordance with the second input.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin information processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 7A-7D, 8A-8B, and9A-9C are, optionally, implemented by components depicted in FIGS. 1A-1Bor FIGS. 10-12. For example, displaying operation 702, receivingoperation 722, detecting operations 730 and 738, updating operation 742,obtaining operation 802, sending operations 806 and 820, detectingoperations 810 and 814, updating operations 812 and 818, receivingoperations 902 and 928, identifying operations 904 and 930, sendingoperations 918 and 932, and/or detecting operations 934 and 936 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method for invoking a digital assistant, performed by a portable electronic device that includes a portable-device display and is in communication with a vehicle display of a vehicle, comprising: at the portable electronic device: displaying a first user interface on the portable-device display; sending, from the portable electronic device to the vehicle display of the vehicle, information for generating a second user interface, the second user interface including an affordance, and the second user interface is visually distinct from the first user interface; while the second user interface is displayed on the vehicle display of the vehicle, detecting an input activating the affordance in the second user interface, and in response to detecting the input activating the affordance displayed within the second user interface on the vehicle display of the vehicle, causing the portable electronic device to invoke a digital assistant; in response to invoking the digital assistant, prompting a user for an audible request; in response to receiving the audible request at the portable electronic device, causing display, within the second user interface, of a digital assistant dialogue box; and subsequently causing display, within the second user interface, of a user interface object associated with a search result; and maintaining the first user interface on the portable-device display.
 2. The method of claim 1, further comprising: displaying, at the portable-device display a user interface object associated with the search result.
 3. The method of claim 1, including: in response to detecting a user touch input at the user interface object associated with the search result, displaying, at the portable-device display, an information box, distinct from the digital assistant dialogue box, which includes additional information about the search result.
 4. The method of claim 3, wherein the information box includes an affordance configured to display further additional information not previously displayed in the information box.
 5. The method of claim 1, including: automatically selecting the user interface object associated with the search result when the audible request matches the search result.
 6. The method of claim 5, wherein at least one criteria for automatically selecting the user interface object associated with the search result is based on geographic proximity.
 7. The method of claim 1, including: causing display, at the vehicle display, a plurality of user interface objects associated with search results.
 8. The method of claim 1, including, in response to detecting a user input corresponding to the user interface object associated with the search result, displaying, at the portable-device display, an information box, distinct from the digital assistant dialogue box, which includes additional information about the search result.
 9. The method of claim 1, wherein the digital assistant dialogue box indicates that the digital assistant is performing a search.
 10. The method of claim 1, wherein the first user interface on the vehicle display of the vehicle shows a current location of the portable electronic device in a map.
 11. The method of claim 1, wherein the audible request is a speech input received at the portable electronic device.
 12. A non-transitory computer readable storage medium storing one or more programs, the one or more programs, comprising instructions, that when executed by a portable electronic device that includes a portable-device display, and is in communication with a vehicle display of a vehicle, cause the portable electronic device to: display a first user interface on the portable-device display; send, from the portable electronic device to the vehicle display of the vehicle, information for generating a second user interface, the second user interface including an affordance, and the second user interface is visually distinct from the first user interface; while the second user interface is displayed on the vehicle display of the vehicle, detect an input activating the affordance in the second user interface, and in response to detecting the input activating the affordance displayed within the second user interface on the vehicle display of the vehicle, cause the portable electronic device to invoke a digital assistant; in response to invoking the digital assistant, prompt a user for an audible request; cause display, within the second user interface, of a digital assistant dialogue box; and subsequently cause display, within the second user interface, of a user interface object associated with a search result; and maintaining the first user interface on the portable-device display.
 13. The non-transitory computer readable storage medium of claim 12, wherein the one or more programs include instructions, that when executed by the portable electronic device, cause the portable electronic device to: display, at the portable-device display a user interface object associated with the search result.
 14. The non-transitory computer readable storage medium of claim 12, wherein the one or more programs include instructions, that when executed by the portable electronic device, cause the portable electronic device to: in response to detecting a user touch input at the user interface object associated with the search result, display, at the portable-device display, an information box, distinct from the digital assistant dialogue box, which includes additional information about the search result.
 15. The non-transitory computer readable storage medium of claim 14, wherein the information box includes an affordance configured to display further additional information not previously displayed in the information box.
 16. The non-transitory computer readable storage medium of claim 12, wherein the one or more programs include instructions, that when executed by the portable electronic device, cause the portable electronic device to: automatically select the user interface object associated with the search result when the audible request matches the search result.
 17. The non-transitory computer readable storage medium of claim 16, wherein at least one criteria for automatically selecting the user interface object associated with the search result is based on geographic proximity.
 18. The non-transitory computer readable storage medium of claim 12, wherein the one or more programs include instructions, that when executed by the portable electronic device, cause the portable electronic device to: cause display, at the vehicle display, a plurality of user interface objects associated with search results.
 19. The non-transitory computer readable storage medium of claim 12, wherein the one or more programs include instructions, that when executed by the portable electronic device, cause the portable electronic device to: display, at the portable-device display, in response to detecting a user input corresponding to the user interface object associated with the search result, an information box, distinct from the digital assistant dialogue box, which includes additional information about the search result.
 20. A portable electronic device, comprising: a portable-device display; one or more processors; memory; and one or more programs, stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a first user interface on the portable-device display; sending, from the portable electronic device to a vehicle display of a vehicle in communication with the portable electronic device, information for generating a second user interface, the second user interface including an affordance, and the second user interface is visually distinct from the first user interface; while the second user interface is displayed on the vehicle display of the vehicle, detecting an input activating the affordance in the second user interface, and in response to detecting the input activating the affordance displayed within the user interface on the vehicle display of the vehicle, causing the portable electronic device to invoke a digital assistant; in response to invoking the digital assistant, prompting a user for an audible request; in response to receiving the audible request at the portable electronic device, causing display, within the user interface, of a digital assistant dialogue box; and subsequently causing display, within the user interface, of a user interface object associated with a search result. 